xtemplate — Greenflagged

High Speed, eXtensible Template Engine lib on browser and nodejs

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

dead_horseyiminghe

Keywords

templatetemplate enginebrowsernodejs

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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance adoption; absence of attestation is not a security concern for this well-established package.	ai	2026/04/24

Versions (showing 87 of 87)

Version	Deps	Published
5.0.11	2 / 1	2023-01-16
5.0.10	2 / 0	2019-08-22
5.0.9	2 / 0	2019-08-09
5.0.8	2 / 0	2019-08-01
5.0.7	2 / 0	2019-08-01
5.0.6	2 / 0	2019-07-31
5.0.5	2 / 0	2019-07-30
5.0.4	2 / 0	2019-07-30
5.0.1	2 / 0	2019-07-30
5.0.0	2 / 0	2019-07-30
4.7.2	1 / 19	2017-05-22
4.6.1	1 / 19	2017-07-12
4.6.0	1 / 19	2016-08-18
4.5.1	1 / 20	2016-02-16
4.5.0	1 / 20	2015-12-23
4.4.2	1 / 20	2015-12-03
4.4.1	1 / 20	2015-12-03
4.4.0	1 / 17	2015-12-03
4.3.1	0 / 25	2015-07-24
4.3.0	0 / 25	2015-05-19
4.2.4	0 / 25	2015-05-07
4.2.3	0 / 25	2015-05-04
4.2.2	0 / 25	2015-04-20
4.2.1	0 / 25	2015-04-08
4.2.0	0 / 25	2015-03-26
4.1.3	0 / 25	2015-01-29
4.1.2	0 / 25	2015-01-29
4.1.1	0 / 25	2015-01-28
4.1.0	0 / 25	2015-01-26
4.0.5	0 / 30	2015-01-22
4.0.4	0 / 30	2015-01-13
4.0.3	0 / 35	2014-12-24
4.0.2	0 / 34	2014-12-22
4.0.1	0 / 34	2014-12-10
4.0.0	0 / 34	2014-12-10
3.7.1	0 / 33	2014-12-02
3.7.0	0 / 33	2014-11-26
3.6.0	0 / 33	2014-11-25
3.5.2	0 / 33	2014-11-05
3.5.1	0 / 33	2014-11-05
3.5.0	0 / 33	2014-11-05
3.4.1	0 / 32	2014-10-20
3.4.0	0 / 32	2014-10-20
3.3.3	0 / 32	2014-10-20
3.3.2	0 / 32	2014-10-20
3.3.1	0 / 32	2014-10-16
3.3.0	0 / 31	2014-09-30
3.2.2	0 / 31	2014-09-29
3.2.1	0 / 31	2014-09-28
3.2.0	0 / 31	2014-09-25
3.1.1	0 / 30	2014-09-23
3.1.0	0 / 30	2014-09-23
3.0.1	0 / 30	2014-09-22
3.0.0	0 / 30	2014-09-22
2.3.2	0 / 30	2014-09-22
2.3.1	0 / 30	2014-09-19
2.3.0	0 / 30	2014-09-19
2.2.6	0 / 30	2014-09-18
2.2.5	0 / 30	2014-09-18
2.2.4	0 / 30	2014-09-18
2.2.3	0 / 30	2014-09-18
2.2.2	0 / 30	2014-09-18
2.2.1	0 / 30	2014-09-18
2.2.0	0 / 30	2014-09-18
2.1.1	0 / 30	2014-09-18
2.1.0	0 / 28	2014-09-18
2.0.6	0 / 28	2014-09-18
2.0.5	0 / 28	2014-09-18
2.0.4	0 / 28	2014-09-17
2.0.3	0 / 28	2014-09-17
2.0.2	0 / 28	2014-09-17
2.0.1	0 / 28	2014-09-17
2.0.0	0 / 28	2014-09-17
1.4.2	0 / 28	2014-09-17
1.4.1	0 / 28	2014-09-17
1.4.0	0 / 28	2014-09-05
1.3.0	0 / 28	2014-09-04
1.2.4	0 / 26	2014-08-28
1.2.2	0 / 24	2014-08-26
1.2.1	0 / 24	2014-08-26
1.1.1	0 / 21	2014-08-22
1.1.0	0 / 20	2014-08-22
1.0.2	0 / 11	2014-08-19
1.0.1	0 / 11	2014-08-19
1.0.0	1 / 0	2014-08-15
0.0.2	0 / 0	2014-08-12
0.0.1	0 / 0	2014-08-12

v5.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.10

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.8

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.4

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.1

3 findings

HIGH New obfuscated file: dist/xtemplate.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/xtemplate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.0

3 findings

HIGH New obfuscated file: dist/xtemplate.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/xtemplate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.2

3 findings

HIGH New obfuscated file: dist/xtemplate.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/xtemplate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.1

3 findings

HIGH New obfuscated file: dist/xtemplate.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/xtemplate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.2

4 findings

HIGH New file with network + code execution: build/index-standalone-debug.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: build/index-standalone.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.1

4 findings

HIGH New file with network + code execution: build/index-standalone-debug.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: build/index-standalone.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: build/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

3 findings

HIGH New file with network + code execution: lib/compiler.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: lib/compiler/parser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

2 findings

HIGH New file with network + code execution: lib/compiler/parser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

2 findings

HIGH New file with network + code execution: lib/compiler/parser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.