@knapsack/renderer-hbs
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): zod is a well-known, trusted schema validation library; no malicious risk. | ai | |
| license | copyleft-license:GPL-2.0-or-later | AI (license): GPL-2.0-or-later is explicitly declared in package.json; stable for this package. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is the core dependency of a Handlebars renderer package; its use is expected and legitimate here. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not enabled org-wide, stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description in this monorepo package; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@knapsack/utils | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is unreliable for monorepo internal deps. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 4.92.24 | 7 / 9 | |
| 4.92.23 | 7 / 9 | |
| 4.92.22 | 7 / 9 | |
| 4.92.21 | 7 / 9 | |
| 4.92.20 | 7 / 9 | |
| 4.92.19 | 7 / 9 | |
| 4.92.18 | 7 / 9 | |
| 4.92.16 | 7 / 9 | |
| 4.92.14 | 7 / 9 | |
| 4.92.12 | 7 / 9 | |
| 4.92.11 | 7 / 9 | |
| 4.92.10 | 7 / 9 | |
| 4.92.8 | 7 / 9 | |
| 4.92.7 | 7 / 9 | |
| 4.92.4 | 7 / 9 | |
| 4.92.3 | 7 / 9 | |
| 4.92.2 | 7 / 9 | |
| 4.92.1 | 7 / 9 | |
| 4.92.0 | 7 / 9 | |
| 4.91.0 | 7 / 9 | |
| 4.89.13 | 7 / 9 | |
| 4.89.11 | 7 / 9 | |
| 4.89.10 | 7 / 9 | |
| 4.89.9 | 7 / 9 | |
| 4.89.8 | 7 / 9 | |
| 4.89.7 | 7 / 9 | |
| 4.89.2 | 7 / 9 | |
| 4.89.1 | 7 / 9 | |
| 4.89.0 | 7 / 9 | |
| 4.88.0 | 7 / 9 | |
| 4.87.9 | 7 / 9 | |
| 4.87.8 | 7 / 9 | |
| 4.87.7 | 7 / 9 | |
| 4.87.6 | 7 / 9 | |
| 4.87.2 | 7 / 9 | |
| 4.87.1 | 7 / 9 | |
| 4.87.0 | 7 / 9 | |
| 4.86.8 | 7 / 9 | |
| 4.86.7 | 7 / 9 | |
| 4.86.1 | 7 / 9 | |
| 4.86.0 | 7 / 9 | |
| 4.85.1 | 7 / 9 | |
| 4.85.0 | 7 / 9 | |
| 4.84.0 | 7 / 9 | |
| 4.83.0 | 7 / 9 | |
| 4.82.3 | 6 / 9 | |
| 4.82.2 | 6 / 9 | |
| 4.82.1 | 6 / 9 | |
| 4.82.0 | 6 / 9 | |
| 4.81.4 | 6 / 9 | |
| 4.81.3 | 6 / 9 |
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.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
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.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.8
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.0
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.9
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.2
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.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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.