template
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:coverage/lcov-report/prettify.js | AI (source-diff): This is Google's prettify.js syntax highlighter, a well-known minified library bundled in lcov HTML coverage reports. It is a dev artifact, not runtime code, and poses no security risk. | ai | |
| provenance | publisher-changed | AI (provenance): doowb is a known collaborator in the jonschlinkert ecosystem with strong track record (1058 approved packages). This 2014 transition is a legitimate maintainer handoff. | ai | |
| dependencies | unvetted-dep:delims | AI (dependencies): delims is a companion utility package by the same author (jonschlinkert); the dependency is consistent with this package's ecosystem and poses no meaningful risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in helpers/methods.js loads user-specified helper files from local filesystem paths — standard pattern for a template engine framework, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): Package predates npm Sigstore provenance by years; absence is expected for this era of publication. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.17.5 | 45 / 22 | |
| 0.17.1 | 46 / 23 | |
| 0.17.0 | 46 / 23 | |
| 0.14.3 | 28 / 22 | |
| 0.14.2 | 28 / 22 | |
| 0.14.1 | 28 / 23 | |
| 0.14.0 | 27 / 23 | |
| 0.13.1 | 26 / 23 | |
| 0.13.0 | 25 / 24 | |
| 0.12.6 | 25 / 22 | |
| 0.12.5 | 25 / 22 | |
| 0.12.4 | 25 / 22 | |
| 0.12.3 | 26 / 22 | |
| 0.12.2 | 26 / 22 | |
| 0.12.1 | 26 / 21 | |
| 0.12.0 | 25 / 21 | |
| 0.11.1 | 24 / 21 | |
| 0.11.0 | 24 / 21 | |
| 0.10.2 | 24 / 21 | |
| 0.10.1 | 24 / 21 | |
| 0.10.0 | 24 / 21 | |
| 0.9.3 | 24 / 21 | |
| 0.9.2 | 24 / 21 | |
| 0.9.1 | 25 / 21 | |
| 0.9.0 | 25 / 21 | |
| 0.8.0 | 24 / 21 | |
| 0.7.1 | 23 / 21 | |
| 0.7.0 | 23 / 20 | |
| 0.6.2 | 23 / 20 | |
| 0.6.1 | 23 / 20 | |
| 0.6.0 | 22 / 20 | |
| 0.5.4 | 20 / 16 | |
| 0.5.3 | 20 / 16 | |
| 0.5.2 | 20 / 16 | |
| 0.5.1 | 20 / 16 | |
| 0.5.0 | 20 / 16 | |
| 0.4.2 | 21 / 14 | |
| 0.4.1 | 21 / 10 | |
| 0.4.0 | 21 / 10 | |
| 0.3.6 | 21 / 10 | |
| 0.3.5 | 21 / 10 | |
| 0.3.4 | 21 / 10 | |
| 0.3.3 | 21 / 10 | |
| 0.3.1 | 20 / 10 | |
| 0.3.0 | 19 / 10 | |
| 0.2.1 | 2 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.8 | 4 / 2 | |
| 0.1.7 | 4 / 2 | |
| 0.1.6 | 4 / 2 | |
| 0.1.5 | 4 / 2 |
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsThis version was published by a different npm account than previous versions on 2014-12-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis version was published by a different npm account than previous versions on 2014-12-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
2 findingsThis version was published by a different npm account than previous versions on 2014-12-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
3 findingsThis version was published by a different npm account than previous versions on 2014-12-01. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2014-11-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
2 findingsThis version was published by a different npm account than previous versions on 2014-11-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
2 findingsThis version was published by a different npm account than previous versions on 2014-11-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
2 findingsThis version was published by a different npm account than previous versions on 2014-11-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.