@near-wallet-selector/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped NEAR org package; 'core' suffix similarity to 'cors' is coincidental, not a squatting attempt. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for cryptographic signature verification, not payload obfuscation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 10.1.4 | 9 / 2 | |
| 10.1.3 | 9 / 2 | |
| 10.1.2 | 9 / 2 | |
| 10.1.1 | 9 / 2 | |
| 10.1.0 | 9 / 2 | |
| 10.0.0 | 9 / 2 |
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.