critters
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build system changed from webpack to microbundle; missing gitHead is a side effect of the new build environment, not a supply-chain indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Both janicklas-ralph and developit are Google contributors listed in package.json; this is a legitimate intra-team maintainer transition within GoogleChromeLabs. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): postcss and css-select are established CSS ecosystem packages; their addition is consistent with critters' purpose as a CSS inlining tool and a documented migration away from the 'css' package. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from 1MB to 202KB is explained by switching from webpack bundling (which inlined deps) to microbundle (which keeps deps external). Not a stub/redirect. | ai | |
| bogus-package | bogus-package | AI (bogus-package): critters is a legitimate package by developit; v0.0.1 is an early placeholder release — sparse metadata is expected at initial publish and does not indicate spam or malice. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description in v0.0.1 is consistent with an initial placeholder release by a well-known publisher; not a spam indicator for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.0.25 | 7 / 2 | |
| 0.0.24 | 7 / 2 | |
| 0.0.23 | 7 / 2 | |
| 0.0.22 | 7 / 2 | |
| 0.0.21 | 8 / 2 | |
| 0.0.20 | 7 / 2 | |
| 0.0.19 | 7 / 2 | |
| 0.0.18 | 7 / 2 | |
| 0.0.17 | 7 / 2 | |
| 0.0.16 | 6 / 2 | |
| 0.0.15 | 6 / 2 | |
| 0.0.14 | 6 / 2 | |
| 0.0.13 | 6 / 1 | |
| 0.0.12 | 6 / 1 | |
| 0.0.11 | 6 / 0 | |
| 0.0.10 | 5 / 20 | |
| 0.0.9 | 5 / 19 | |
| 0.0.8 | 6 / 19 | |
| 0.0.7 | 5 / 19 | |
| 0.0.6 | 5 / 19 | |
| 0.0.5 | 10 / 19 | |
| 0.0.4 | 10 / 19 | |
| 0.0.3 | 10 / 19 | |
| 0.0.2 | 10 / 19 | |
| 0.0.1 | 0 / 4 |
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
2 findingsCVSS 6.1 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ### Impact Critters version 0.0.17-0.0.19 have an issue when parsing the HTML which leads to a potential [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) bug. ### Patches The bug has been fixed in `v0.0.20`. ### Workarounds Upgrading Critters version to `>0.0.20` is the easiest fix. This is a non breaking version upgrade so we recommend all users to use `v0.0.20`.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
2 findingsCVSS 6.1 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ### Impact Critters version 0.0.17-0.0.19 have an issue when parsing the HTML which leads to a potential [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) bug. ### Patches The bug has been fixed in `v0.0.20`. ### Workarounds Upgrading Critters version to `>0.0.20` is the easiest fix. This is a non breaking version upgrade so we recommend all users to use `v0.0.20`.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
2 findingsCVSS 6.1 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N ### Impact Critters version 0.0.17-0.0.19 have an issue when parsing the HTML which leads to a potential [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) bug. ### Patches The bug has been fixed in `v0.0.20`. ### Workarounds Upgrading Critters version to `>0.0.20` is the easiest fix. This is a non breaking version upgrade so we recommend all users to use `v0.0.20`.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: developit.
This version was published by a different npm account than previous versions on 2022-01-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: developit.
This version was published by a different npm account than previous versions on 2021-11-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: developit.
This version was published by a different npm account than previous versions on 2021-10-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: developit.
This version was published by a different npm account than previous versions on 2021-10-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: developit.
This version was published by a different npm account than previous versions on 2021-10-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
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: janicklas-ralph.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.