openapi-format
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): Mature package with long track record; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.33.5 | 5 / 3 | |
| 1.33.4 | 5 / 3 | |
| 1.33.3 | 5 / 3 | |
| 1.33.2 | 5 / 3 | |
| 1.33.1 | 5 / 3 | |
| 1.33.0 | 5 / 3 | |
| 1.32.1 | 5 / 3 | |
| 1.32.0 | 5 / 3 | |
| 1.31.0 | 5 / 3 | |
| 1.30.1 | 5 / 3 | |
| 1.30.0 | 5 / 3 | |
| 1.29.5 | 5 / 3 | |
| 1.29.4 | 5 / 2 | |
| 1.29.3 | 5 / 2 | |
| 1.29.2 | 5 / 2 | |
| 1.29.1 | 6 / 2 | |
| 1.29.0 | 6 / 2 | |
| 1.28.0 | 6 / 2 | |
| 1.27.3 | 6 / 2 | |
| 1.27.2 | 6 / 2 | |
| 1.27.1 | 6 / 2 | |
| 1.27.0 | 6 / 2 | |
| 1.26.0 | 6 / 2 | |
| 1.25.4 | 6 / 2 | |
| 1.25.3 | 6 / 2 | |
| 1.25.2 | 6 / 2 | |
| 1.25.1 | 6 / 2 | |
| 1.25.0 | 6 / 2 | |
| 1.24.2 | 5 / 2 | |
| 1.24.1 | 5 / 2 | |
| 1.24.0 | 5 / 2 | |
| 1.23.2 | 4 / 1 | |
| 1.23.1 | 4 / 1 | |
| 1.23.0 | 4 / 1 | |
| 1.22.5 | 4 / 1 | |
| 1.22.4 | 4 / 1 | |
| 1.22.3 | 4 / 1 | |
| 1.22.2 | 4 / 1 | |
| 1.22.1 | 4 / 1 | |
| 1.22.0 | 4 / 1 | |
| 1.21.2 | 4 / 1 | |
| 1.21.1 | 4 / 1 | |
| 1.21.0 | 4 / 1 | |
| 1.20.0 | 4 / 1 | |
| 1.19.0 | 4 / 1 | |
| 1.18.0 | 4 / 1 | |
| 1.17.2 | 4 / 1 | |
| 1.17.1 | 4 / 1 |
v1.33.5
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
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.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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
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.