@solana/wallet-adapter-wallets
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@solana/wallet-adapter-sollet | AI (dependencies): Official sibling package in same Solana wallet-adapter monorepo, not third-party. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Aggregator/meta-package; sparse README and no keywords are expected for this monorepo sub-package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.19.38 | 36 / 2 | |
| 0.19.37 | 36 / 2 | |
| 0.19.36 | 36 / 2 | |
| 0.19.35 | 36 / 2 | |
| 0.19.34 | 36 / 2 | |
| 0.19.33 | 36 / 2 | |
| 0.18.2 | 40 / 0 | |
| 0.18.1 | 39 / 0 | |
| 0.18.0 | 38 / 0 | |
| 0.17.2 | 39 / 0 | |
| 0.17.1 | 38 / 0 | |
| 0.17.0 | 33 / 0 | |
| 0.16.10 | 33 / 0 | |
| 0.16.9 | 30 / 0 | |
| 0.16.8 | 29 / 0 | |
| 0.16.6 | 29 / 0 | |
| 0.16.5 | 29 / 0 | |
| 0.16.4 | 28 / 0 | |
| 0.16.3 | 27 / 0 | |
| 0.16.1 | 20 / 0 | |
| 0.16.0 | 19 / 0 | |
| 0.15.5 | 19 / 0 | |
| 0.15.4 | 17 / 0 | |
| 0.15.3 | 17 / 0 | |
| 0.15.2 | 17 / 0 | |
| 0.15.1 | 17 / 0 | |
| 0.15.0 | 17 / 0 | |
| 0.14.3 | 17 / 0 | |
| 0.14.2 | 17 / 0 | |
| 0.14.1 | 17 / 0 | |
| 0.14.0 | 17 / 0 | |
| 0.13.0 | 16 / 1 | |
| 0.8.0 | 12 / 1 | |
| 0.7.6 | 12 / 1 | |
| 0.7.5 | 11 / 1 | |
| 0.7.4 | 11 / 1 | |
| 0.7.3 | 9 / 1 | |
| 0.7.2 | 9 / 1 | |
| 0.7.1 | 10 / 1 | |
| 0.7.0 | 9 / 1 | |
| 0.6.2 | 8 / 1 | |
| 0.6.1 | 7 / 1 | |
| 0.6.0 | 7 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.1.0 | 7 / 0 |
v0.19.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jordansexton) than the most recent previously approved version (steveluscher) on 2022-07-27, but jordansexton is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.16.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steveluscher) than the most recent previously approved version (jordansexton) on 2022-07-13, but steveluscher is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.