@usecapsule/core-sdk
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jordymcnabnityastboschphtoweladitisriramkwi25nsquare
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:qs | AI (phantom-deps): qs is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; stable pattern for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the @usecapsule scoped SDK family; sparse metadata is consistent across all versions, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across 124 versions of this scoped SDK package; not a malice signal. | ai |
v2.20.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.