@types/bson
5
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Stub types package from trusted @types publisher; sparse metadata is normal. | ai | |
| phantom-deps | phantom-dep:bson | AI (phantom-deps): Stub types package declares bson as peer dep by design, not a real import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 1 / 0 | |
| 4.2.3 | 1 / 0 | |
| 4.2.2 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 |
v4.2.3
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.
v4.2.2
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.
v4.2.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.