very-small-parser
A very small Markdown, HTML, and CSS parser.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): dist/index.js is a standard webpack-minified bundle produced by the package's documented build process; long lines are minification artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/module.js | AI (source-diff): dist/module.js is a standard webpack-minified ESM bundle produced by the package's documented build process; long lines are minification artifacts, not obfuscation. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 0 / 12 | |
| 1.14.0 | 0 / 11 | |
| 1.13.0 | 0 / 11 | |
| 1.12.0 | 0 / 11 | |
| 1.11.0 | 0 / 11 | |
| 1.10.0 | 0 / 11 | |
| 1.9.0 | 0 / 11 | |
| 1.8.0 | 0 / 11 | |
| 1.7.0 | 0 / 11 | |
| 1.6.0 | 0 / 11 | |
| 1.5.0 | 0 / 11 | |
| 1.4.0 | 0 / 11 | |
| 1.3.0 | 0 / 11 | |
| 1.2.0 | 0 / 11 | |
| 1.1.0 | 0 / 11 | |
| 1.0.0 | 0 / 7 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.