@netlify/open-api
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Netlify org package with bot publisher and clean history; dormancy likely reflects API stability, not abandonment. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.57.0 | 0 / 17 | |
| 2.56.1 | 0 / 17 | |
| 2.56.0 | 0 / 17 | |
| 2.55.0 | 0 / 17 | |
| 2.54.0 | 0 / 17 | |
| 2.53.0 | 0 / 17 | |
| 2.52.0 | 0 / 17 | |
| 2.51.0 | 0 / 17 | |
| 2.50.0 | 0 / 17 | |
| 2.49.2 | 0 / 17 | |
| 2.49.1 | 0 / 17 | |
| 2.49.0 | 0 / 17 | |
| 2.48.0 | 0 / 17 | |
| 2.47.0 | 0 / 17 | |
| 2.46.0 | 0 / 17 | |
| 2.45.0 | 0 / 17 | |
| 2.44.0 | 0 / 17 | |
| 2.43.1 | 0 / 17 | |
| 2.43.0 | 0 / 17 | |
| 2.42.0 | 0 / 17 | |
| 2.41.0 | 0 / 17 | |
| 2.40.0 | 0 / 17 | |
| 2.39.0 | 0 / 17 | |
| 2.38.0 | 0 / 17 | |
| 2.37.0 | 0 / 17 | |
| 2.36.0 | 0 / 17 | |
| 2.35.1 | 0 / 17 | |
| 2.35.0 | 0 / 17 | |
| 2.34.0 | 0 / 17 | |
| 2.33.1 | 0 / 16 | |
| 2.33.0 | 0 / 16 | |
| 2.32.0 | 0 / 16 | |
| 2.31.0 | 0 / 16 |
v2.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.