@e-mc/task
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): Established package with 207 versions; no provenance is consistent across all releases. | ai |
Versions (showing 51 of 175)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 1 / 0 | |
| 0.14.4 | 1 / 0 | |
| 0.14.3 | 1 / 0 | |
| 0.14.2 | 1 / 0 | |
| 0.14.1 | 1 / 0 | |
| 0.14.0 | 1 / 0 | |
| 0.13.11 | 1 / 0 | |
| 0.13.10 | 1 / 0 | |
| 0.13.9 | 1 / 0 | |
| 0.13.8 | 1 / 0 | |
| 0.13.7 | 1 / 0 | |
| 0.13.6 | 1 / 0 | |
| 0.13.5 | 1 / 0 | |
| 0.13.4 | 1 / 0 | |
| 0.13.3 | 1 / 0 | |
| 0.13.2 | 1 / 0 | |
| 0.13.1 | 1 / 0 | |
| 0.13.0 | 1 / 0 | |
| 0.12.17 | 1 / 0 | |
| 0.12.16 | 1 / 0 | |
| 0.12.15 | 1 / 0 | |
| 0.12.14 | 1 / 0 | |
| 0.12.13 | 1 / 0 | |
| 0.12.12 | 1 / 0 | |
| 0.12.11 | 1 / 0 | |
| 0.12.10 | 1 / 0 | |
| 0.12.9 | 1 / 0 | |
| 0.12.8 | 1 / 0 | |
| 0.12.7 | 1 / 0 | |
| 0.12.6 | 1 / 0 | |
| 0.12.5 | 1 / 0 | |
| 0.12.4 | 1 / 0 | |
| 0.12.3 | 1 / 0 | |
| 0.12.2 | 1 / 0 | |
| 0.12.1 | 1 / 0 | |
| 0.12.0 | 1 / 0 | |
| 0.11.18 | 1 / 0 | |
| 0.11.17 | 1 / 0 | |
| 0.11.16 | 1 / 0 | |
| 0.11.15 | 1 / 0 | |
| 0.11.14 | 1 / 0 | |
| 0.11.13 | 1 / 0 | |
| 0.11.12 | 1 / 0 | |
| 0.11.11 | 1 / 0 | |
| 0.11.10 | 1 / 0 | |
| 0.11.9 | 1 / 0 | |
| 0.11.8 | 1 / 0 | |
| 0.11.7 | 1 / 0 | |
| 0.11.5 | 1 / 0 | |
| 0.11.4 | 1 / 0 | |
| 0.11.3 | 1 / 0 |
v0.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.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.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.