@getpara/solana-wallet-connectors
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this monorepo package; not a malice signal. | ai | |
| phantom-deps | phantom-dep:@getpara/web-sdk | AI (phantom-deps): Same-org monorepo dep; may be re-exported rather than directly imported in this connector package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of established @getpara SDK suite; sparse metadata is typical for scoped SDK sub-packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 7 | |
| 3.0.0 | 3 / 7 | |
| 2.32.1 | 3 / 7 | |
| 2.32.0 | 3 / 7 | |
| 2.31.0 | 3 / 7 | |
| 2.28.0 | 3 / 7 | |
| 2.27.0 | 3 / 7 | |
| 2.23.0 | 3 / 7 | |
| 2.22.0 | 3 / 7 | |
| 2.21.0 | 3 / 7 | |
| 2.20.0 | 3 / 7 | |
| 2.14.0 | 3 / 7 | |
| 2.13.0 | 3 / 7 | |
| 2.12.0 | 3 / 7 | |
| 2.11.0 | 3 / 7 | |
| 2.10.0 | 3 / 7 | |
| 2.8.0 | 3 / 7 | |
| 2.7.0 | 3 / 7 | |
| 2.6.0 | 3 / 7 | |
| 2.5.0 | 3 / 7 | |
| 2.4.0 | 3 / 7 | |
| 2.3.0 | 3 / 7 | |
| 2.2.0 | 3 / 7 | |
| 2.1.0 | 3 / 7 | |
| 2.0.0 | 3 / 7 |
v3.1.0
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 (nsquare) than the most recent previously approved version (tbosch) on 2026-06-05, but nsquare 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.
v3.0.0
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 (tbosch) than the most recent previously approved version (nsquare) on 2026-05-28, but tbosch 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.
v2.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.