@dynamic-labs/solana-extension
```bash npm install @dynamic-labs/solana-extension ```
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @dynamic-labs packages; org publishes without Sigstore attestation by policy. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Published via GitHub Actions CI/CD with no code changes; dormancy pattern consistent with release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/types | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic commonly misfires on type-only imports in this monorepo. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/webview-messages | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic commonly misfires on indirect/re-exported usage in this monorepo. | ai |
Versions (showing 51 of 132)
| Version | Deps | Published |
|---|---|---|
| 4.88.0 | 7 / 0 | |
| 4.87.2 | 7 / 0 | |
| 4.87.1 | 7 / 0 | |
| 4.84.0 | 7 / 0 | |
| 4.83.1 | 7 / 0 | |
| 4.83.0 | 7 / 0 | |
| 4.81.0 | 7 / 0 | |
| 4.80.0 | 7 / 0 | |
| 4.79.2 | 7 / 0 | |
| 4.79.0 | 7 / 0 | |
| 4.49.0 | 7 / 0 | |
| 4.48.2 | 7 / 0 | |
| 4.48.1 | 7 / 0 | |
| 4.48.0 | 7 / 0 | |
| 4.47.3 | 7 / 0 | |
| 4.47.2 | 7 / 0 | |
| 4.47.1 | 7 / 0 | |
| 4.47.0 | 7 / 0 | |
| 4.46.3 | 7 / 0 | |
| 4.46.2 | 7 / 0 | |
| 4.46.1 | 7 / 0 | |
| 4.46.0 | 7 / 0 | |
| 4.45.3 | 6 / 0 | |
| 4.45.2 | 6 / 0 | |
| 4.45.1 | 6 / 0 | |
| 4.45.0 | 6 / 0 | |
| 4.44.4 | 6 / 0 | |
| 4.44.3 | 6 / 0 | |
| 4.44.2 | 6 / 0 | |
| 4.44.1 | 6 / 0 | |
| 4.44.0 | 6 / 0 | |
| 4.43.0 | 6 / 0 | |
| 4.42.0 | 6 / 0 | |
| 4.41.1 | 6 / 0 | |
| 4.41.0 | 6 / 0 | |
| 4.40.2 | 6 / 0 | |
| 4.40.1 | 6 / 0 | |
| 4.40.0 | 6 / 0 | |
| 4.39.0 | 6 / 0 | |
| 4.38.0 | 6 / 0 | |
| 4.37.2 | 6 / 0 | |
| 4.37.1 | 6 / 0 | |
| 4.37.0 | 6 / 0 | |
| 4.36.1 | 6 / 0 | |
| 4.36.0 | 6 / 0 | |
| 4.35.0 | 6 / 0 | |
| 4.34.0 | 6 / 0 | |
| 4.33.0 | 6 / 0 | |
| 4.32.1 | 6 / 0 | |
| 4.32.0 | 6 / 0 | |
| 4.31.4 | 6 / 0 |
v4.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.