headers-polyfill
A native "Headers" class polyfill.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher (kettanaito) with 205 approved packages and 0 rejections. Missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Low-severity process finding; package is from a well-known, trusted publisher in the mswjs ecosystem. Absence of Sigstore attestation is not a security risk here. | ai | |
| dependencies | unvetted-dep:@types/set-cookie-parser | AI (dependencies): @types/set-cookie-parser is a DefinitelyTyped package — a standard, benign TypeScript type definition. Its use as a runtime dep is a known pattern for re-exported types. | ai | |
| phantom-deps | phantom-dep:@types/set-cookie-parser | AI (phantom-deps): Type-only dependency used by convention; not directly imported in source but legitimately declared. Stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 2 / 6 | |
| 5.0.0 | 2 / 6 | |
| 4.0.3 | 0 / 11 | |
| 4.0.2 | 0 / 11 | |
| 4.0.1 | 0 / 11 | |
| 4.0.0 | 0 / 11 | |
| 3.3.0 | 0 / 11 | |
| 3.2.5 | 0 / 11 | |
| 3.2.4 | 0 / 11 | |
| 3.2.3 | 0 / 11 | |
| 3.2.2 | 0 / 10 | |
| 3.2.1 | 2 / 8 | |
| 3.2.0 | 0 / 8 | |
| 3.1.2 | 0 / 8 | |
| 3.1.1 | 0 / 8 | |
| 3.1.0 | 0 / 8 | |
| 3.0.10 | 0 / 7 | |
| 3.0.9 | 0 / 7 | |
| 3.0.8 | 0 / 5 | |
| 3.0.7 | 0 / 5 | |
| 3.0.6 | 0 / 5 | |
| 3.0.5 | 0 / 5 | |
| 3.0.4 | 0 / 5 | |
| 3.0.3 | 0 / 5 |
v3.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kettanaito.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.