Sign In

inferbench-cli

Package Overview
Dependencies
Maintainers
2
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

inferbench-cli - npm Package Compare versions

Comparing version
0.1.2
to
0.1.3
+5
-2
package.json
{
"name": "inferbench-cli",
"version": "0.1.2",
"version": "0.1.3",
"description": "Benchmarks local-LLM-inference engines (omlx, llama.cpp) on your own hardware, live, and recommends the fastest engine/config combination for your model.",

@@ -25,3 +25,6 @@ "keywords": [

"license": "Apache-2.0",
"author": "",
"author": "Rudrendu Paul",
"contributors": [
"Sourav Nandy"
],
"type": "module",

@@ -28,0 +31,0 @@ "bin": {

@@ -59,15 +59,8 @@ # InferBench

**Honest note on current status**: both packages are code-complete,
tested, and built, but neither publish has cleared its registry yet, for
two separate and unrelated registry-side reasons. The npm package's
publish is blocked by a transient npm-registry rate limit (`E429`) --
unrelated to code readiness; the npm code itself was already built and
verified from a local tarball install. The PyPI package's first publish
attempt hit PyPI's own new-project-creation abuse limit (`429 Too many new
projects created`) on this account -- also a registry-side throttle, not a
packaging problem; the wheel and sdist were built, `twine check`-verified,
and installed + run end to end against real `omlx` and `llama.cpp`
binaries on real hardware before that attempt. Both publishes will be
retried once their respective registry-side limits clear -- see
[`python/README.md`](./python/README.md) and
**Current status**: both packages are published and installable today.
`npm install -g inferbench-cli` and `pip install inferbench-cli` both
work -- see
[npmjs.com/package/inferbench-cli](https://www.npmjs.com/package/inferbench-cli)
and [pypi.org/project/inferbench-cli](https://pypi.org/project/inferbench-cli/),
or [`python/README.md`](./python/README.md) and
[docs/getting-started.md](./docs/getting-started.md) for the Python-specific

@@ -74,0 +67,0 @@ walkthrough, and [CHANGELOG.md](./CHANGELOG.md) for each distribution's