@starknet-react/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @starknet-react/core is a scoped Starknet React library; Levenshtein match to 'cors' is a false positive. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 192.168.1.44 appears only in a test fixture file, not production code. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.0.3 | 7 / 12 | |
| 5.0.2 | 7 / 12 | |
| 5.0.1 | 7 / 12 | |
| 5.0.0 | 7 / 12 |
v5.0.3
2 findingsPackage name '@starknet-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
2 findingsPackage name '@starknet-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
2 findingsPackage name '@starknet-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
2 findingsPackage name '@starknet-react/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.