@farcaster/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @farcaster/core is a legitimate Farcaster protocol package, not a typosquat of cors. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 6 / 9 | |
| 0.18.11 | 6 / 9 | |
| 0.18.10 | 6 / 9 | |
| 0.18.9 | 6 / 9 | |
| 0.18.8 | 6 / 9 | |
| 0.18.7 | 6 / 9 | |
| 0.17.1 | 6 / 9 | |
| 0.17.0 | 6 / 9 | |
| 0.16.5 | 6 / 9 |
v0.19.0
2 findingsPackage name '@farcaster/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.11
2 findingsPackage name '@farcaster/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.10
2 findingsPackage name '@farcaster/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.9
2 findingsPackage name '@farcaster/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.
v0.18.8
2 findingsPackage name '@farcaster/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.
v0.18.7
2 findingsPackage name '@farcaster/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.
v0.17.1
2 findingsPackage name '@farcaster/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.
v0.17.0
2 findingsPackage name '@farcaster/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.
v0.16.5
2 findingsPackage name '@farcaster/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.