@midnight-ntwrk/wallet-sdk-facade
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @midnight-ntwrk packages; org publishes from GitHub artifacts repo without Sigstore attestation. | ai | |
| phantom-deps | phantom-dep:@midnight-ntwrk/wallet-sdk-hd | AI (phantom-deps): Same-org facade package; deps likely re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@midnight-ntwrk/wallet-sdk-abstractions | AI (phantom-deps): Same-org facade package; deps likely re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@midnight-ntwrk/wallet-sdk-address-format | AI (phantom-deps): Same-org facade package; deps likely re-exported rather than directly imported. | ai |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.