@starknet-io/get-starknet-core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 4 / 2 | |
| 4.0.8 | 3 / 6 | |
| 4.0.7 | 3 / 6 | |
| 4.0.6 | 3 / 6 | |
| 4.0.5 | 3 / 6 | |
| 4.0.4 | 3 / 6 | |
| 4.0.3 | 2 / 6 | |
| 4.0.2 | 2 / 6 | |
| 4.0.1 | 2 / 6 | |
| 4.0.0 | 2 / 6 |
v4.0.7
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 (amanusk) than the most recent previously approved version (z-dan) on 2025-03-27, but amanusk 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.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.