xtemplate
High Speed, eXtensible Template Engine lib on browser and nodejs
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 | net-exec-file:dist/xtemplate.js | AI (source-diff): The net+exec pattern fires on webpack's dynamic require mechanism in the bundle. No actual network calls or dropper behavior present. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/xtemplate.js | AI (source-diff): dist/xtemplate.js is a standard webpack UMD bundle produced by the documented pub script. Long lines are minified webpack output, not obfuscation. Stable false positive for this package. | ai | |
| source-diff | net-exec-file:build/index-standalone-debug.js | AI (source-diff): File is a legitimate debug build artifact of the xtemplate engine. 'net-exec' pattern triggered by globalEval used for template rendering, not actual network+dropper behavior. | ai | |
| source-diff | obfuscated-file:build/index.js | AI (source-diff): Minified build artifact of the xtemplate template engine. Standard minification output for browser distribution. | ai | |
| source-diff | obfuscated-file:build/index-standalone.js | AI (source-diff): Minified browser-ready build of the xtemplate template engine. Long lines are standard minification output, not malicious obfuscation. | ai | |
| source-diff | net-exec-file:lib/compiler.js | AI (source-diff): lib/compiler.js is the template engine's AST-to-JS compiler — dynamic code generation is core functionality, not malware. No actual network calls in the file. | ai | |
| source-diff | net-exec-file:lib/compiler/parser.js | AI (source-diff): parser.js is a generated artifact from the kison parser generator (a devDependency). The file contains standard parser boilerplate, not malicious network+exec code. This is a stable false positive for xtemplate. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): cp.exec() in gulpfile.js runs git commands for release automation only; not reachable by package consumers. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is confined to gulpfile.js for a git tagging release task; never executed at install or runtime by consumers. Stable false positive for this build tooling pattern. | ai | |
| provenance | missing-githead | AI (provenance): Established package with trusted publisher; missing gitHead reflects a workflow change, not a security risk. No other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; absence of attestation is not a security concern for this well-established package. | ai |
Versions (showing 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 5.0.11 | 2 / 1 | |
| 5.0.10 | 2 / 0 | |
| 5.0.9 | 2 / 0 | |
| 5.0.8 | 2 / 0 | |
| 5.0.7 | 2 / 0 | |
| 5.0.6 | 2 / 0 | |
| 5.0.5 | 2 / 0 | |
| 5.0.4 | 2 / 0 | |
| 5.0.1 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.7.2 | 1 / 19 | |
| 4.6.1 | 1 / 19 | |
| 4.6.0 | 1 / 19 | |
| 4.5.1 | 1 / 20 | |
| 4.5.0 | 1 / 20 | |
| 4.4.2 | 1 / 20 | |
| 4.4.1 | 1 / 20 | |
| 4.4.0 | 1 / 17 | |
| 4.3.1 | 0 / 25 | |
| 4.3.0 | 0 / 25 | |
| 4.2.4 | 0 / 25 | |
| 4.2.3 | 0 / 25 | |
| 4.2.2 | 0 / 25 | |
| 4.2.1 | 0 / 25 | |
| 4.2.0 | 0 / 25 | |
| 4.1.3 | 0 / 25 | |
| 4.1.2 | 0 / 25 | |
| 4.1.1 | 0 / 25 | |
| 4.1.0 | 0 / 25 | |
| 4.0.5 | 0 / 30 | |
| 4.0.4 | 0 / 30 | |
| 4.0.3 | 0 / 35 | |
| 4.0.2 | 0 / 34 | |
| 4.0.1 | 0 / 34 | |
| 4.0.0 | 0 / 34 | |
| 3.7.1 | 0 / 33 | |
| 3.7.0 | 0 / 33 | |
| 3.6.0 | 0 / 33 | |
| 3.5.2 | 0 / 33 | |
| 3.5.1 | 0 / 33 | |
| 3.5.0 | 0 / 33 | |
| 3.4.1 | 0 / 32 | |
| 3.4.0 | 0 / 32 | |
| 3.3.3 | 0 / 32 | |
| 3.3.2 | 0 / 32 | |
| 3.3.1 | 0 / 32 | |
| 3.3.0 | 0 / 31 | |
| 3.2.2 | 0 / 31 | |
| 3.2.1 | 0 / 31 | |
| 3.2.0 | 0 / 31 | |
| 3.1.1 | 0 / 30 |
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v5.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v5.0.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v5.0.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: yiminghe.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v4.7.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yiminghe.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.