@zuplo/openapi-tools
Tooling for OpenAPI files
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): zod, semver, and jsonpath-plus are all well-established, widely-trusted packages appropriate for an OpenAPI tooling library. No malicious signal. | ai | |
| dependencies | unvetted-dep:jsonpath-plus | AI (dependencies): jsonpath-plus is a well-known JSONPath library; its use in an OpenAPI tooling package is expected and appropriate across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @zuplo scoped package with 589 versions and 4.5k weekly downloads; cosmetic README/keyword signals are not indicative of spam. | ai |
Versions (showing 100 of 506)
| Version | Deps | Published |
|---|---|---|
| 6.62.1 | 5 / 6 | |
| 6.61.23 | 5 / 6 | |
| 6.61.22 | 5 / 6 | |
| 6.61.21 | 5 / 6 | |
| 6.61.20 | 5 / 6 | |
| 6.61.19 | 5 / 6 | |
| 6.61.17 | 5 / 6 | |
| 6.61.16 | 5 / 6 | |
| 6.61.15 | 5 / 6 | |
| 6.61.14 | 5 / 6 | |
| 6.61.12 | 5 / 6 | |
| 6.61.11 | 5 / 6 | |
| 6.61.10 | 5 / 6 | |
| 6.61.9 | 5 / 6 | |
| 6.61.8 | 5 / 6 | |
| 6.61.7 | 5 / 6 | |
| 6.61.6 | 5 / 6 | |
| 6.61.5 | 5 / 6 | |
| 6.61.4 | 5 / 6 | |
| 6.61.3 | 5 / 6 | |
| 6.61.2 | 5 / 6 | |
| 6.61.1 | 5 / 6 | |
| 6.61.0 | 5 / 6 | |
| 6.60.37 | 5 / 6 | |
| 6.60.36 | 5 / 6 | |
| 6.60.35 | 5 / 6 | |
| 6.60.33 | 5 / 6 | |
| 6.60.32 | 5 / 6 | |
| 6.60.30 | 5 / 6 | |
| 6.60.29 | 5 / 6 | |
| 6.60.28 | 5 / 6 | |
| 6.60.27 | 5 / 6 | |
| 6.60.26 | 5 / 6 | |
| 6.60.25 | 5 / 6 | |
| 6.60.24 | 5 / 6 | |
| 6.60.23 | 5 / 6 | |
| 6.60.22 | 5 / 6 | |
| 6.60.21 | 5 / 6 | |
| 6.60.20 | 5 / 6 | |
| 6.60.19 | 5 / 6 | |
| 6.60.18 | 5 / 6 | |
| 6.60.17 | 5 / 6 | |
| 6.60.16 | 5 / 6 | |
| 6.60.15 | 5 / 6 | |
| 6.60.14 | 5 / 6 | |
| 6.60.13 | 5 / 6 | |
| 6.60.12 | 5 / 6 | |
| 6.60.11 | 5 / 6 | |
| 6.60.10 | 5 / 6 | |
| 6.60.9 | 5 / 6 | |
| 6.60.8 | 5 / 6 | |
| 6.60.6 | 5 / 6 | |
| 6.60.4 | 5 / 6 | |
| 6.60.3 | 5 / 6 | |
| 6.60.2 | 5 / 6 | |
| 6.60.1 | 5 / 6 | |
| 6.59.62 | 5 / 6 | |
| 6.59.61 | 5 / 6 | |
| 6.59.60 | 5 / 6 | |
| 6.59.59 | 5 / 6 | |
| 6.59.58 | 5 / 6 | |
| 6.59.56 | 5 / 6 | |
| 6.59.55 | 5 / 6 | |
| 6.59.54 | 5 / 6 | |
| 6.59.53 | 5 / 6 | |
| 6.59.52 | 5 / 6 | |
| 6.59.51 | 5 / 6 | |
| 6.59.50 | 5 / 6 | |
| 6.59.49 | 5 / 6 | |
| 6.59.48 | 5 / 6 | |
| 6.59.47 | 5 / 6 | |
| 6.59.45 | 5 / 6 | |
| 6.59.44 | 5 / 6 | |
| 6.59.43 | 5 / 6 | |
| 6.59.42 | 5 / 6 | |
| 6.59.41 | 5 / 6 | |
| 6.59.39 | 5 / 6 | |
| 6.59.37 | 5 / 6 | |
| 6.59.36 | 5 / 6 | |
| 6.59.35 | 5 / 6 | |
| 6.59.34 | 5 / 6 | |
| 6.59.33 | 5 / 6 | |
| 6.59.32 | 5 / 6 | |
| 6.59.31 | 5 / 6 | |
| 6.59.30 | 5 / 6 | |
| 6.59.29 | 5 / 6 | |
| 6.59.28 | 5 / 6 | |
| 6.59.27 | 5 / 6 | |
| 6.59.25 | 5 / 6 | |
| 6.59.23 | 5 / 6 | |
| 6.59.22 | 5 / 6 | |
| 6.59.21 | 5 / 6 | |
| 6.59.20 | 5 / 6 | |
| 6.59.19 | 5 / 6 | |
| 6.59.18 | 5 / 6 | |
| 6.59.17 | 5 / 6 | |
| 6.59.13 | 5 / 6 | |
| 6.59.12 | 5 / 6 | |
| 6.59.11 | 5 / 6 | |
| 6.59.10 | 5 / 6 |
v6.61.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.61.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.61.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.60.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.60.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.59.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.59.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.59.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.59.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.