es6template
Easy and small template engine for the browser.
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:tunnckocore | AI (email-domain): The tunnckoCore reference is a legacy author attribution handle, not an active maintainer email. Package is published by zalmoxisus who has a strong track record; domain claim would not grant npm publish access. | ai |
v1.0.5
2 findingsMaintainer email '@tunnckoCore' uses domain 'tunnckocore' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.