@openapi-contrib/json-schema-to-openapi-schema
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package now publishes via GitHub Actions CI/CD with SLSA attestation; jonluca is the listed author — legitimate automation transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jonluca is the package author per package.json; addition reflects legitimate ownership, not a takeover. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.3.3 | 3 / 17 | |
| 4.3.2 | 3 / 17 | |
| 4.3.1 | 3 / 17 | |
| 4.3.0 | 3 / 17 | |
| 4.2.0 | 3 / 17 | |
| 4.1.0 | 3 / 17 |
v4.3.3
2 findingsThis version was published by a different npm account than previous versions on 2026-06-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.