@becomposable/client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Enforces pnpm usage only; no code execution or network fetch. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): JWT payload decode for expiry check, standard auth pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party scoped rename of existing dep, same version pin. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped monorepo package, metadata gaps are cosmetic. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.42.2 | 4 / 5 | |
| 0.42.1 | 4 / 5 | |
| 0.42.0 | 4 / 5 | |
| 0.41.0 | 4 / 5 | |
| 0.40.0 | 4 / 5 | |
| 0.39.1 | 4 / 5 | |
| 0.39.0 | 4 / 5 | |
| 0.38.4 | 4 / 5 | |
| 0.38.3 | 4 / 5 | |
| 0.38.2 | 4 / 5 | |
| 0.38.1 | 4 / 5 | |
| 0.38.0 | 4 / 5 | |
| 0.37.0 | 4 / 5 | |
| 0.36.1 | 4 / 5 | |
| 0.36.0 | 4 / 5 | |
| 0.35.0 | 4 / 5 | |
| 0.34.0 | 4 / 5 | |
| 0.33.0 | 4 / 5 | |
| 0.32.0 | 4 / 5 | |
| 0.31.0 | 4 / 5 | |
| 0.30.1 | 4 / 5 | |
| 0.30.0 | 4 / 5 |
v0.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
2 findingsScript: pnpm exec only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.