@beeos-ai/cli
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @beeos-ai/cli is clearly branded for the BeeOS AI product; Levenshtein match to 'joi' is a false positive with no impersonation intent. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool that delegates to platform-specific native binaries; child_process use is expected and consistent with the package's purpose and architecture. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 10 / 8 | |
| 1.1.0 | 10 / 8 | |
| 1.0.24 | 10 / 8 | |
| 1.0.23 | 10 / 8 | |
| 1.0.22 | 10 / 8 | |
| 1.0.21 | 10 / 8 | |
| 1.0.20 | 10 / 8 | |
| 1.0.19 | 10 / 8 | |
| 1.0.18 | 10 / 8 | |
| 1.0.17 | 10 / 8 | |
| 1.0.16 | 10 / 8 | |
| 1.0.15 | 10 / 8 | |
| 1.0.14 | 10 / 8 | |
| 1.0.13 | 10 / 8 | |
| 1.0.12 | 10 / 8 | |
| 1.0.11 | 10 / 8 | |
| 1.0.10 | 10 / 8 | |
| 1.0.9 | 10 / 8 | |
| 1.0.8 | 10 / 8 | |
| 1.0.7 | 10 / 8 | |
| 1.0.6 | 10 / 8 | |
| 1.0.5 | 10 / 8 | |
| 1.0.4 | 10 / 8 | |
| 1.0.3 | 10 / 8 | |
| 1.0.2 | 9 / 8 | |
| 0.1.2 | 0 / 0 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.