@bossmode/cli
Run BossMode locally on your machine. Bridges to your existing Claude Code SDK or Codex CLI subscription.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cockpit-dist/assets/index-y8G_0DQZ.js | AI (source-diff): Standard Vite/Rollup minified bundle for embedded web UI; samples show React/scheduler code with MIT headers. | ai | |
| source-diff | obfuscated-file:dist/cockpit-dist/assets/query-BXmq1W2r.js | AI (source-diff): Standard minified react-query bundle; samples show recognizable library code with MIT headers. | ai | |
| source-diff | obfuscated-file:dist/cockpit-dist/assets/router-hNRHgxTs.js | AI (source-diff): Standard minified React router bundle; samples show recognizable library code with MIT headers. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @bossmode/cli is a scoped CLI package with no relation to joi; the Levenshtein match is a coincidental string similarity, not impersonation. | ai |
v0.7.2
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bossmode.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.