@midnight-ntwrk/wallet-sdk-unshielded-wallet
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:@midnight-ntwrk/wallet-sdk-hd | AI (phantom-deps): Same-org dependency; likely used transitively or in type declarations rather than direct imports. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has 13 approved packages with no rejections. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 9 / 1 | |
| 3.0.0 | 9 / 1 | |
| 2.1.0 | 9 / 1 | |
| 2.0.0 | 9 / 1 | |
| 1.0.0 | 9 / 8 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.