@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, so a manually published version cannot be tied back to a reviewed commit.
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 100 of 663)
| Version | Deps | Published |
|---|---|---|
| 4.85.0 | 8 / 11 | |
| 4.84.0 | 8 / 11 | |
| 4.83.0 | 8 / 11 | |
| 4.82.3 | 7 / 11 | |
| 4.82.2 | 7 / 11 | |
| 4.82.1 | 7 / 11 | |
| 4.82.0 | 7 / 11 | |
| 4.81.5 | 7 / 11 | |
| 4.81.4 | 7 / 11 | |
| 4.81.3 | 7 / 11 | |
| 4.81.2 | 7 / 11 | |
| 4.81.1 | 7 / 11 | |
| 4.81.0 | 7 / 11 | |
| 4.80.20 | 7 / 11 | |
| 4.80.19 | 7 / 11 | |
| 4.80.18 | 7 / 11 | |
| 4.80.17 | 7 / 11 | |
| 4.80.16 | 7 / 11 | |
| 4.80.15 | 7 / 11 | |
| 4.80.14 | 7 / 11 | |
| 4.80.13 | 7 / 11 | |
| 4.80.12 | 7 / 11 | |
| 4.80.11 | 7 / 11 | |
| 4.80.10 | 7 / 11 | |
| 4.80.9 | 7 / 11 | |
| 4.80.8 | 7 / 11 | |
| 4.80.7 | 7 / 11 | |
| 4.80.6 | 7 / 11 | |
| 4.80.5 | 7 / 11 | |
| 4.80.4 | 7 / 11 | |
| 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 | |
| 4.78.14 | 6 / 11 | |
| 4.78.13 | 6 / 11 | |
| 4.78.12 | 6 / 11 | |
| 4.78.11 | 6 / 11 | |
| 4.78.10 | 6 / 11 | |
| 4.78.9 | 6 / 11 | |
| 4.78.8 | 6 / 11 | |
| 4.78.7 | 6 / 12 | |
| 4.78.6 | 6 / 12 | |
| 4.78.5 | 6 / 12 | |
| 4.78.4 | 6 / 12 | |
| 4.78.3 | 6 / 12 | |
| 4.78.2 | 6 / 12 | |
| 4.78.1 | 6 / 12 | |
| 4.78.0 | 6 / 12 | |
| 4.77.0 | 6 / 12 | |
| 4.76.3 | 6 / 12 | |
| 4.76.2 | 6 / 12 | |
| 4.76.1 | 6 / 12 | |
| 4.76.0 | 6 / 12 | |
| 4.75.9 | 6 / 12 | |
| 4.75.8 | 6 / 12 | |
| 4.75.7 | 6 / 12 | |
| 4.75.6 | 6 / 12 | |
| 4.75.5 | 6 / 12 | |
| 4.75.4 | 6 / 12 | |
| 4.75.3 | 6 / 12 | |
| 4.75.2 | 6 / 12 | |
| 4.75.1 | 6 / 12 | |
| 4.75.0 | 6 / 12 | |
| 4.74.0 | 6 / 12 | |
| 4.73.0 | 6 / 12 | |
| 4.72.1 | 6 / 12 | |
| 4.72.0 | 6 / 12 | |
| 4.71.18 | 6 / 12 | |
| 4.71.17 | 6 / 12 | |
| 4.71.16 | 6 / 12 | |
| 4.71.15 | 6 / 12 | |
| 4.71.14 | 6 / 12 | |
| 4.71.13 | 6 / 12 | |
| 4.71.12 | 6 / 12 | |
| 4.71.11 | 6 / 12 | |
| 4.71.10 | 6 / 12 | |
| 4.71.9 | 6 / 12 | |
| 4.71.8 | 6 / 12 | |
| 4.71.7 | 6 / 12 | |
| 4.71.5 | 6 / 12 | |
| 4.71.4 | 6 / 12 | |
| 4.71.3 | 6 / 12 | |
| 4.71.2 | 6 / 12 | |
| 4.71.1 | 6 / 12 | |
| 4.71.0 | 6 / 12 | |
| 4.70.6 | 6 / 12 | |
| 4.70.5 | 6 / 12 | |
| 4.70.4 | 6 / 12 | |
| 4.70.3 | 6 / 12 | |
| 4.70.2 | 6 / 12 | |
| 4.70.1 | 6 / 12 | |
| 4.70.0 | 6 / 12 | |
| 4.69.14 | 6 / 12 | |
| 4.69.13 | 6 / 12 | |
| 4.69.12 | 6 / 12 | |
| 4.69.11 | 6 / 12 |
v4.78.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.69.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.69.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.69.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.69.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.