@midnight-ntwrk/wallet-sdk-shielded
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): SDK monorepo pattern; ws referenced in config/transitive context, not a direct import. | ai | |
| phantom-deps | phantom-dep:scale-ts | AI (phantom-deps): SDK monorepo pattern; scale-ts referenced in config/transitive context. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): SDK monorepo pattern; node-fetch referenced in config/transitive context. | ai | |
| phantom-deps | phantom-dep:@scure/base | AI (phantom-deps): SDK monorepo pattern; @scure/base referenced in config/transitive context. | ai | |
| phantom-deps | phantom-dep:isomorphic-ws | AI (phantom-deps): SDK monorepo pattern; isomorphic-ws referenced in config/transitive context. | ai | |
| provenance | no-provenance | AI (provenance): Midnight Foundation org package; provenance absence is common and no other risk signals present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 9 / 0 | |
| 3.0.0 | 9 / 0 | |
| 2.1.0 | 9 / 0 | |
| 2.0.0 | 9 / 0 | |
| 1.0.0 | 16 / 17 |
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.