@dynamic-labs/starknet-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:starknet | AI (dependencies): starknet is the canonical StarkNet JS SDK; stable dependency for this package across versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 387 versions; published via GitHub Actions CI which is standard for this org. | ai |
Versions (showing 7 of 208)
| Version | Deps | Published |
|---|---|---|
| 4.18.4 | 4 / 0 | |
| 4.18.3 | 4 / 0 | |
| 4.18.2 | 4 / 0 | |
| 4.18.1 | 4 / 0 | |
| 4.18.0 | 4 / 0 | |
| 4.17.0 | 4 / 0 | |
| 4.16.0 | 4 / 0 |
v4.18.4
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.18.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.18.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.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.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.17.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.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.