@knapsack/renderer-angular
Render Angular
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:@knapsack/app | AI (dependencies): Same-org monorepo sibling pinned to identical version; consistent pattern across all Knapsack packages. | ai | |
| dependencies | unvetted-dep:@knapsack/types | AI (dependencies): Same-org monorepo sibling pinned to identical version. | ai | |
| dependencies | unvetted-dep:@knapsack/utils | AI (dependencies): Same-org monorepo sibling pinned to identical version. | ai | |
| dependencies | unvetted-dep:@knapsack/spec-utils | AI (dependencies): Same-org monorepo sibling pinned to identical version. | ai | |
| dependencies | unvetted-dep:@knapsack/renderer-webpack-base | AI (dependencies): Same-org monorepo sibling pinned to identical version. | ai |
Versions (showing 7 of 117)
| Version | Deps | Published |
|---|---|---|
| 4.80.3 | 6 / 11 | |
| 4.80.2 | 6 / 11 | |
| 4.80.1 | 6 / 11 | |
| 4.80.0 | 6 / 11 | |
| 4.79.2 | 6 / 11 | |
| 4.79.1 | 6 / 11 | |
| 4.79.0 | 6 / 11 |
v4.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.