@knapsack/renderer-twig
Render Twig
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@basalt/twig-renderer | AI (dependencies): Long-standing dependency of this package; stable across versions with no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; no provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 7 / 5 | |
| 4.92.24 | 7 / 5 | |
| 4.92.23 | 7 / 5 | |
| 4.92.21 | 7 / 5 | |
| 4.92.20 | 7 / 5 | |
| 4.92.19 | 7 / 5 | |
| 4.92.17 | 7 / 5 | |
| 4.92.16 | 7 / 5 | |
| 4.92.15 | 7 / 5 | |
| 4.92.14 | 7 / 5 | |
| 4.92.11 | 7 / 5 | |
| 4.92.10 | 7 / 5 | |
| 4.92.9 | 7 / 5 | |
| 4.92.8 | 7 / 5 | |
| 4.92.7 | 7 / 5 | |
| 4.92.6 | 7 / 5 | |
| 4.92.2 | 7 / 5 | |
| 4.92.0 | 7 / 5 | |
| 4.91.0 | 7 / 5 | |
| 4.90.0 | 7 / 5 | |
| 4.89.13 | 7 / 5 | |
| 4.89.11 | 7 / 5 | |
| 4.89.10 | 7 / 5 | |
| 4.89.9 | 7 / 5 | |
| 4.89.7 | 7 / 5 | |
| 4.89.5 | 7 / 5 | |
| 4.89.2 | 7 / 5 | |
| 4.88.0 | 7 / 5 | |
| 4.87.8 | 7 / 5 | |
| 4.87.7 | 7 / 5 | |
| 4.87.6 | 7 / 5 | |
| 4.87.5 | 7 / 5 | |
| 4.87.4 | 7 / 5 | |
| 4.87.3 | 7 / 5 | |
| 4.87.1 | 7 / 5 | |
| 4.87.0 | 7 / 5 | |
| 4.86.8 | 7 / 5 | |
| 4.86.7 | 7 / 5 | |
| 4.86.6 | 7 / 5 | |
| 4.86.5 | 7 / 5 | |
| 4.86.4 | 7 / 5 | |
| 4.86.3 | 7 / 5 | |
| 4.86.2 | 7 / 5 | |
| 4.86.1 | 7 / 5 | |
| 4.86.0 | 7 / 5 | |
| 4.85.9 | 7 / 5 | |
| 4.85.8 | 7 / 5 | |
| 4.85.7 | 7 / 5 | |
| 4.85.6 | 7 / 5 | |
| 4.85.5 | 7 / 5 | |
| 4.85.4 | 7 / 5 |
v4.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.86.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.