@3mo/field
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 versions of this package; publisher has 26 approved packages without provenance. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 5 / 1 | |
| 0.6.2 | 5 / 1 | |
| 0.6.1 | 5 / 1 | |
| 0.6.0 | 5 / 1 | |
| 0.5.2 | 6 / 1 | |
| 0.5.1 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.7 | 6 / 1 | |
| 0.2.6 | 5 / 1 | |
| 0.2.5 | 5 / 1 |
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.