insert-css
insert a string of css into the <head>
7
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
jonaskellosubstackvvo
Keywords
cssinsertdombrowserbrowserifyinjectstylesstylesheetstylehtmlheadlink
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from substack to vvo in 2016; vvo is a well-established publisher with extensive track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vvo added as maintainer in 2016; well-known npm publisher with 749 approved versions. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; no CI/CD provenance expected for 2016-era publishes. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 0 / 6 | |
| 1.1.0 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.2.0 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 1 | |
| 0.0.0 | 0 / 2 |
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.0
2 findings
HIGH
Publisher changed: substack → vvo (on 2016-06-26)
provenance
This version was published by a different npm account than previous versions on 2016-06-26. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.