eta
Lightweight, fast, and powerful embedded JS template engine
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/core.js | AI (source-diff): dist/core.js is tsdown-minified bundle output for this template engine; size-limit config confirms intentional minification. Stable FP for this package. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): eta is a well-known template engine with 2.2M weekly downloads; the Levenshtein proximity to 'koa' is coincidental — completely different domains and no impersonation intent. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.6.0 | 0 / 8 | |
| 4.5.1 | 0 / 8 | |
| 4.5.0 | 0 / 8 | |
| 4.4.1 | 0 / 8 | |
| 4.4.0 | 0 / 8 | |
| 4.3.1 | 0 / 8 | |
| 4.3.0 | 0 / 8 | |
| 4.2.0 | 0 / 8 | |
| 4.1.0 | 0 / 8 | |
| 4.0.1 | 0 / 8 | |
| 4.0.0 | 0 / 8 | |
| 3.5.0 | 0 / 26 | |
| 3.4.1 | 0 / 26 | |
| 3.4.0 | 0 / 26 | |
| 3.3.0 | 0 / 26 | |
| 3.2.0 | 0 / 26 | |
| 3.1.1 | 0 / 26 | |
| 3.1.0 | 0 / 26 | |
| 3.0.3 | 0 / 26 | |
| 3.0.2 | 0 / 26 | |
| 3.0.1 | 0 / 27 | |
| 3.0.0 | 0 / 27 |
v4.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.