@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, so a manually published version cannot be tied back to a reviewed commit.
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 14 of 214)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 5 / 0 | |
| 4.4.2 | 5 / 0 | |
| 4.4.1 | 5 / 0 | |
| 4.4.0 | 5 / 0 | |
| 4.3.2 | 5 / 0 | |
| 4.3.1 | 5 / 0 | |
| 4.3.0 | 5 / 0 | |
| 4.2.3 | 5 / 0 | |
| 4.2.2 | 5 / 0 | |
| 4.2.1 | 5 / 0 | |
| 4.2.0 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 |
v4.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.