xtpl
nodejs wrapper around xtemplate engine
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): Established package by trusted publisher yiminghe; missing gitHead is a publish-environment change, not a malicious indicator. No other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security risk, for this well-established package by a trusted publisher. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 3.4.2 | 0 / 10 | |
| 3.4.1 | 0 / 10 | |
| 3.4.0 | 0 / 10 | |
| 3.3.0 | 0 / 10 | |
| 3.2.0 | 0 / 9 | |
| 3.1.9 | 0 / 9 | |
| 3.1.8 | 0 / 9 | |
| 3.1.7 | 0 / 9 | |
| 3.1.6 | 0 / 9 | |
| 3.1.5 | 0 / 9 | |
| 3.1.4 | 0 / 9 | |
| 3.1.3 | 0 / 9 | |
| 3.1.2 | 0 / 9 | |
| 3.1.1 | 0 / 9 | |
| 3.1.0 | 0 / 9 | |
| 3.0.0 | 0 / 9 | |
| 2.1.0 | 0 / 9 | |
| 2.0.3 | 0 / 7 | |
| 2.0.2 | 0 / 7 | |
| 2.0.1 | 0 / 7 | |
| 2.0.0 | 0 / 7 | |
| 1.1.3 | 1 / 6 | |
| 1.1.2 | 1 / 6 | |
| 1.1.1 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.0 | 1 / 6 | |
| 0.17.2 | 1 / 6 | |
| 0.17.1 | 1 / 1 | |
| 0.17.0 | 1 / 1 | |
| 0.16.0 | 1 / 1 | |
| 0.15.2 | 1 / 1 | |
| 0.15.0 | 1 / 1 | |
| 0.14.0 | 1 / 1 | |
| 0.13.0 | 3 / 5 | |
| 0.12.1 | 1 / 1 | |
| 0.12.0 | 1 / 1 | |
| 0.11.0 | 1 / 1 | |
| 0.10.0 | 1 / 1 | |
| 0.9.5 | 1 / 1 | |
| 0.9.4 | 1 / 1 | |
| 0.9.3 | 1 / 1 | |
| 0.9.2 | 0 / 1 | |
| 0.9.1 | 0 / 1 | |
| 0.9.0 | 0 / 1 | |
| 0.8.0 | 0 / 1 | |
| 0.7.3 | 0 / 1 | |
| 0.7.2 | 0 / 1 | |
| 0.7.0 | 0 / 1 | |
| 0.6.0 | 0 / 1 | |
| 0.5.0 | 0 / 1 | |
| 0.4.1 | 0 / 1 |
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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.
v3.1.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.
v3.0.0
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.
v2.1.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.
v2.0.3
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.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.