has-cors
Detects support for Cross-Origin Resource Sharing
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
shtylman
Keywords
corscrossoriginresourcesharingdomain
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:global | AI (npm-metadata): URL dep points to a pinned tarball at a specific tag on the official component GitHub org — same org as has-cors. Stable pattern from the component.js era; not a meaningful supply-chain risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4470 days old; lack of provenance is expected for packages predating Sigstore on npm. | ai |
v1.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.