@ibm-cloud/openapi-ruleset
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established IBM Cloud package; lack of provenance is consistent across all versions and poses no elevated risk here. | ai | |
| dependencies | unvetted-dep:@ibm-cloud/openapi-ruleset-utilities | AI (dependencies): Same IBM org sibling package; stable dependency relationship across many versions. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1.33.12 | 12 / 2 | |
| 1.33.11 | 12 / 2 | |
| 1.33.10 | 12 / 2 | |
| 1.33.9 | 12 / 2 | |
| 1.33.8 | 12 / 2 | |
| 1.33.7 | 12 / 2 | |
| 1.33.6 | 12 / 2 | |
| 1.33.5 | 12 / 2 | |
| 1.33.4 | 12 / 2 | |
| 1.33.3 | 12 / 2 | |
| 1.33.2 | 12 / 2 | |
| 1.33.1 | 12 / 2 | |
| 1.33.0 | 12 / 2 | |
| 1.32.1 | 12 / 2 | |
| 1.32.0 | 11 / 2 | |
| 1.31.2 | 11 / 2 | |
| 1.31.1 | 11 / 2 | |
| 1.31.0 | 11 / 2 | |
| 1.30.1 | 11 / 2 | |
| 1.30.0 | 11 / 2 | |
| 1.29.4 | 11 / 2 | |
| 1.29.3 | 11 / 2 | |
| 1.29.2 | 11 / 2 | |
| 1.29.1 | 11 / 2 | |
| 1.29.0 | 11 / 2 | |
| 1.28.4 | 10 / 2 | |
| 1.28.3 | 10 / 2 | |
| 1.28.2 | 10 / 2 | |
| 1.28.1 | 10 / 2 | |
| 1.28.0 | 10 / 2 | |
| 1.27.0 | 10 / 2 | |
| 1.26.0 | 10 / 2 | |
| 1.25.2 | 10 / 2 | |
| 1.25.1 | 10 / 2 | |
| 1.25.0 | 10 / 2 | |
| 1.24.0 | 10 / 2 | |
| 1.23.3 | 10 / 2 | |
| 1.23.2 | 10 / 2 | |
| 1.23.1 | 10 / 2 | |
| 1.23.0 | 10 / 2 | |
| 1.22.0 | 10 / 2 | |
| 1.21.2 | 10 / 2 | |
| 1.21.1 | 10 / 2 | |
| 1.21.0 | 10 / 2 | |
| 1.20.0 | 10 / 2 | |
| 1.19.0 | 10 / 2 | |
| 1.18.2 | 10 / 2 | |
| 1.18.1 | 10 / 2 | |
| 1.18.0 | 10 / 2 | |
| 1.17.1 | 10 / 2 | |
| 1.17.0 | 10 / 2 |
v1.33.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.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.
v1.17.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.