@0xsequence/wallet-primitives
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): Fires on legitimate blockchain explorer URLs in network config; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of @0xsequence monorepo; missing metadata is cosmetic, not indicative of malice. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a style issue, not a risk signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.11 | 1 / 5 | |
| 3.0.10 | 1 / 5 | |
| 3.0.9 | 1 / 5 | |
| 3.0.8 | 1 / 5 | |
| 3.0.7 | 1 / 5 | |
| 3.0.6 | 1 / 5 | |
| 3.0.5 | 1 / 5 | |
| 3.0.4 | 1 / 5 | |
| 3.0.3 | 1 / 5 | |
| 3.0.2 | 1 / 5 | |
| 3.0.1 | 1 / 5 | |
| 3.0.0 | 1 / 5 |
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.