@bsv/paymail
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jest | AI (phantom-deps): Test framework; referenced in config/scripts only, not runtime import. | ai | |
| phantom-deps | phantom-dep:ts2md | AI (phantom-deps): Doc generation tool; used in npm scripts only. | ai | |
| phantom-deps | phantom-dep:ts-jest | AI (phantom-deps): Test transform; config-only usage. | ai | |
| phantom-deps | phantom-dep:supertest | AI (phantom-deps): Test utility; not imported at runtime. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Fetch polyfill; cross-fetch is the runtime dep; node-fetch is redundant but benign. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build tool; config/scripts only. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Type definitions for test framework; no runtime import. | ai | |
| phantom-deps | phantom-dep:tsconfig-to-dual-package | AI (phantom-deps): Build tool used in build script only. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 12 / 4 | |
| 2.3.0 | 12 / 4 | |
| 2.2.5 | 12 / 1 | |
| 2.1.2 | 12 / 1 | |
| 2.1.1 | 12 / 1 |
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.