@knapsack/renderer-native-android
Native Android component renderer for Knapsack
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Knapsack monorepo packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 4 / 6 | |
| 4.98.0 | 4 / 6 | |
| 4.97.0 | 4 / 6 | |
| 4.96.7 | 4 / 6 | |
| 4.96.6 | 4 / 6 | |
| 4.96.5 | 4 / 6 | |
| 4.96.4 | 4 / 6 | |
| 4.96.3 | 4 / 6 | |
| 4.96.2 | 4 / 6 | |
| 4.96.1 | 4 / 6 | |
| 4.96.0 | 4 / 6 | |
| 4.95.1 | 4 / 6 | |
| 4.95.0 | 4 / 6 | |
| 4.94.13 | 4 / 6 | |
| 4.94.12 | 4 / 6 | |
| 4.94.11 | 4 / 6 | |
| 4.94.10 | 4 / 6 | |
| 4.94.9 | 4 / 6 | |
| 4.94.8 | 4 / 6 | |
| 4.94.7 | 4 / 6 | |
| 4.94.6 | 4 / 6 | |
| 4.94.5 | 4 / 6 | |
| 4.94.4 | 4 / 6 | |
| 4.94.3 | 4 / 6 | |
| 4.94.2 | 4 / 6 | |
| 4.94.1 | 4 / 6 | |
| 4.94.0 | 4 / 6 | |
| 4.93.3 | 4 / 6 | |
| 4.93.2 | 4 / 6 | |
| 4.93.1 | 4 / 6 | |
| 4.93.0 | 4 / 6 | |
| 4.92.24 | 4 / 6 | |
| 4.92.23 | 4 / 6 | |
| 4.92.22 | 4 / 6 | |
| 4.92.21 | 4 / 6 | |
| 4.92.20 | 4 / 6 | |
| 4.92.19 | 4 / 6 | |
| 4.92.18 | 4 / 6 | |
| 4.92.17 | 4 / 6 | |
| 4.92.16 | 4 / 6 | |
| 4.92.15 | 4 / 6 | |
| 4.92.14 | 4 / 6 | |
| 4.92.13 | 4 / 6 | |
| 4.92.12 | 4 / 6 | |
| 4.92.11 | 4 / 6 | |
| 4.92.10 | 4 / 6 | |
| 4.92.9 | 4 / 6 | |
| 4.92.8 | 4 / 6 | |
| 4.92.7 | 4 / 6 | |
| 4.92.6 | 4 / 6 | |
| 4.92.5 | 4 / 6 |
v4.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.95.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.95.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.94.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.94.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.94.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.94.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.