@deepfuture/dui-primitives
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @deepfuture packages; absence of provenance is not a risk signal for this org. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 3 / 0 | |
| 1.9.1 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.4 | 3 / 0 | |
| 1.8.3 | 3 / 0 | |
| 1.8.2 | 3 / 0 | |
| 1.8.1 | 3 / 0 | |
| 1.8.0 | 3 / 0 | |
| 1.7.0 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.0 | 3 / 0 | |
| 1.3.0 | 3 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.0 | 3 / 0 | |
| 1.0.0 | 3 / 0 |
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.