@getbeebase/cli
Beebase CLI — manage projects, keys, schemas, organizations
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/cli.cjs | AI (source-diff): dist/cli.cjs is produced by esbuild --minify per the build script; minification is expected and the code is readable CLI tooling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is explicitly an internal tool (UNLICENSED, no public repo); missing README/keywords/homepage are expected for private tooling. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: @getbeebase/cli is a scoped BaaS CLI tool with no semantic relationship to the joi validation library. The Levenshtein match is coincidental. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.17.1 | 6 / 1 | |
| 0.17.0 | 6 / 0 | |
| 0.8.8 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.3 | 6 / 0 | |
| 0.6.2 | 6 / 0 | |
| 0.6.1 | 6 / 0 | |
| 0.5.2 | 6 / 0 | |
| 0.5.1 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.1 | 6 / 0 | |
| 0.4.0 | 6 / 0 |
v0.17.1
2 findingsNewly 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.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.