conjure-lite
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established package with 27 versions; metadata gaps are cosmetic, not indicative of spam or malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable package with 27 versions; missing description is a cosmetic issue only. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to elevate this concern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 0 / 19 | |
| 0.7.2 | 0 / 19 | |
| 0.7.1 | 0 / 19 | |
| 0.7.0 | 0 / 19 | |
| 0.6.1 | 0 / 19 | |
| 0.6.0 | 0 / 19 | |
| 0.5.0 | 0 / 19 | |
| 0.4.4 | 0 / 16 | |
| 0.4.3 | 0 / 16 | |
| 0.4.0 | 2 / 10 | |
| 0.3.3 | 2 / 10 | |
| 0.3.2 | 2 / 10 | |
| 0.3.1 | 2 / 10 | |
| 0.3.0 | 2 / 10 | |
| 0.2.1 | 2 / 10 | |
| 0.2.0 | 2 / 10 | |
| 0.1.1 | 2 / 8 | |
| 0.0.6 | 2 / 8 | |
| 0.0.5 | 2 / 8 | |
| 0.0.4 | 2 / 8 | |
| 0.0.3 | 2 / 8 | |
| 0.0.2 | 2 / 8 |
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.4.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.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.