@reown/appkit-adapter-solana
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wallet-standard/wallet | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-siwe | AI (phantom-deps): Monorepo package; @reown/* deps are re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-scaffold-ui | AI (phantom-deps): Monorepo package; @reown/* deps are re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@walletconnect/utils | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-ui | AI (phantom-deps): Monorepo package; @reown/* deps are re-exported or used transitively. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with org migration, not takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account; expected in migration. | ai | |
| provenance | publisher-changed | AI (provenance): Org-wide publisher migration with strong track record; no code changes in diff. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 1.8.23 | 17 / 8 | |
| 1.8.22 | 17 / 8 | |
| 1.8.21 | 17 / 8 | |
| 1.8.20 | 17 / 8 | |
| 1.8.19 | 17 / 8 | |
| 1.8.18 | 17 / 8 | |
| 1.8.17 | 17 / 8 | |
| 1.8.16 | 17 / 8 | |
| 1.8.15 | 17 / 8 | |
| 1.8.14 | 17 / 8 | |
| 1.8.13 | 17 / 8 | |
| 1.8.12 | 17 / 8 | |
| 1.8.11 | 17 / 8 | |
| 1.8.10 | 17 / 8 | |
| 1.8.9 | 17 / 8 | |
| 1.8.8 | 17 / 8 | |
| 1.8.7 | 17 / 8 | |
| 1.8.6 | 17 / 8 | |
| 1.8.5 | 17 / 8 | |
| 1.8.4 | 17 / 8 | |
| 1.8.3 | 17 / 8 | |
| 1.8.2 | 17 / 8 | |
| 1.8.1 | 17 / 8 | |
| 1.8.0 | 17 / 8 | |
| 1.7.20 | 17 / 8 | |
| 1.7.19 | 17 / 8 | |
| 1.7.18 | 17 / 8 | |
| 1.7.17 | 17 / 8 | |
| 1.7.16 | 17 / 8 | |
| 1.7.15 | 17 / 8 | |
| 1.7.14 | 16 / 8 | |
| 1.7.13 | 16 / 8 | |
| 1.7.12 | 16 / 8 | |
| 1.7.11 | 16 / 8 | |
| 1.7.10 | 16 / 8 | |
| 1.7.9 | 16 / 8 | |
| 1.7.8 | 16 / 8 | |
| 1.7.7 | 16 / 8 | |
| 1.7.6 | 16 / 8 | |
| 1.7.5 | 16 / 8 | |
| 1.7.4 | 16 / 8 | |
| 1.7.3 | 16 / 8 | |
| 1.7.2 | 16 / 8 | |
| 1.7.1 | 16 / 8 | |
| 1.7.0 | 16 / 8 | |
| 1.6.9 | 20 / 8 | |
| 1.6.8 | 20 / 8 | |
| 1.6.7 | 20 / 8 | |
| 1.6.6 | 20 / 8 | |
| 1.6.5 | 20 / 8 | |
| 1.6.4 | 20 / 8 |
v1.8.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.