@near-wallet-selector/my-near-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@near-js/accounts | AI (dependencies): @near-js/accounts is a first-party NEAR protocol library; expected dependency for this wallet selector package. | ai | |
| provenance | no-provenance | AI (provenance): Established NEAR org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 10.1.4 | 7 / 0 | |
| 10.1.3 | 7 / 0 | |
| 10.1.2 | 7 / 0 | |
| 10.1.1 | 7 / 0 | |
| 10.1.0 | 7 / 0 | |
| 10.0.0 | 7 / 0 |
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.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.
v10.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.