@colijnit/sharedapi
1
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
yury.sjilliscitralf.eversenelskedaan.vdjpatrickvkeulen
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:request | AI (phantom-deps): Declared dep; phantom-dep heuristic fires on config references, not a real risk here. | ai | |
| phantom-deps | phantom-dep:jsencrypt | AI (phantom-deps): Declared dep; same config-reference false positive pattern. | ai | |
| phantom-deps | phantom-dep:rxjs-compat | AI (phantom-deps): Declared dep; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package; sparse README/keywords are expected, not spam indicators. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.20 | 6 / 11 |
v1.0.20
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.