@oclif/plugin-search
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): Salesforce/oclif is a well-known, trusted publisher. Lack of Sigstore provenance is not a meaningful risk for this established package. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 1.2.53 | 3 / 22 | |
| 1.2.52 | 3 / 22 | |
| 1.2.51 | 3 / 22 | |
| 1.2.50 | 3 / 22 | |
| 1.2.49 | 3 / 22 | |
| 1.2.48 | 3 / 22 | |
| 1.2.47 | 3 / 22 | |
| 1.2.46 | 3 / 22 | |
| 1.2.45 | 3 / 22 | |
| 1.2.44 | 3 / 22 | |
| 1.2.43 | 3 / 22 | |
| 1.2.42 | 3 / 22 | |
| 1.2.41 | 3 / 22 | |
| 1.2.40 | 3 / 22 | |
| 1.2.39 | 3 / 22 | |
| 1.2.38 | 3 / 22 | |
| 1.2.37 | 3 / 22 | |
| 1.2.36 | 3 / 22 | |
| 1.2.35 | 3 / 22 | |
| 1.2.34 | 3 / 22 | |
| 1.2.33 | 3 / 22 | |
| 1.2.32 | 3 / 22 | |
| 1.2.31 | 3 / 22 | |
| 1.2.30 | 3 / 22 | |
| 1.2.29 | 3 / 22 | |
| 1.2.28 | 3 / 22 | |
| 1.2.27 | 3 / 22 | |
| 1.2.26 | 3 / 22 | |
| 1.2.25 | 3 / 22 | |
| 1.2.24 | 3 / 22 | |
| 1.2.23 | 3 / 22 | |
| 1.2.22 | 3 / 22 | |
| 1.2.21 | 3 / 22 | |
| 1.2.20 | 3 / 22 | |
| 1.2.19 | 3 / 22 | |
| 1.2.18 | 3 / 22 | |
| 1.2.17 | 3 / 22 | |
| 1.2.16 | 3 / 22 | |
| 1.2.15 | 3 / 22 | |
| 1.2.14 | 3 / 22 | |
| 1.2.13 | 3 / 22 | |
| 1.2.12 | 3 / 22 | |
| 1.2.11 | 3 / 22 | |
| 1.2.10 | 3 / 22 | |
| 1.2.9 | 3 / 22 | |
| 1.2.8 | 3 / 22 | |
| 1.2.7 | 3 / 22 | |
| 1.2.6 | 3 / 22 | |
| 1.2.5 | 3 / 22 | |
| 1.2.4 | 3 / 22 | |
| 1.2.3 | 3 / 22 |
v1.2.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.