@omnigraph/openapi
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation is the expected pattern for this monorepo; not a takeover signal. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation confirms legitimate CI/CD publishing pipeline. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with strong provenance; missing description is stable metadata quirk, not malware indicator. | ai | |
| dependencies | unvetted-dep:@omnigraph/json-schema | AI (dependencies): Sibling omnigraph package from the same monorepo; not a risk. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/cross-helpers | AI (dependencies): Core graphql-mesh package from the same monorepo; not a risk. | ai | |
| dependencies | unvetted-dep:json-machete | AI (dependencies): Part of the graphql-mesh monorepo ecosystem; stable dependency pattern across versions. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/string-interpolation | AI (dependencies): Core graphql-mesh package from the same monorepo; not a risk. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/fusion-composition | AI (dependencies): Core graphql-mesh package from the same monorepo; not a risk. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/types | AI (dependencies): Core graphql-mesh package from the same monorepo; not a risk. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/utils | AI (dependencies): Core graphql-mesh package from the same monorepo; not a risk. | ai |
Versions (showing 74 of 274)
| Version | Deps | Published |
|---|---|---|
| 0.17.3 | 9 / 0 | |
| 0.17.2 | 9 / 0 | |
| 0.17.1 | 9 / 0 | |
| 0.17.0 | 9 / 0 | |
| 0.16.10 | 9 / 0 | |
| 0.16.9 | 9 / 0 | |
| 0.16.8 | 9 / 0 | |
| 0.16.7 | 9 / 0 | |
| 0.16.6 | 9 / 0 | |
| 0.16.5 | 9 / 0 | |
| 0.16.4 | 9 / 0 | |
| 0.16.3 | 9 / 0 | |
| 0.16.2 | 9 / 0 | |
| 0.16.1 | 9 / 0 | |
| 0.16.0 | 9 / 0 | |
| 0.15.4 | 9 / 0 | |
| 0.15.3 | 9 / 0 | |
| 0.15.2 | 9 / 0 | |
| 0.15.1 | 9 / 0 | |
| 0.15.0 | 9 / 0 | |
| 0.14.11 | 9 / 0 | |
| 0.14.10 | 9 / 0 | |
| 0.14.9 | 9 / 0 | |
| 0.14.8 | 9 / 0 | |
| 0.14.7 | 9 / 0 | |
| 0.14.6 | 9 / 0 | |
| 0.14.5 | 9 / 0 | |
| 0.14.4 | 9 / 0 | |
| 0.14.3 | 9 / 0 | |
| 0.14.2 | 9 / 0 | |
| 0.14.1 | 9 / 0 | |
| 0.14.0 | 9 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.12.0 | 9 / 0 | |
| 0.11.2 | 9 / 0 | |
| 0.11.1 | 9 / 0 | |
| 0.11.0 | 9 / 0 | |
| 0.10.0 | 9 / 0 | |
| 0.9.0 | 9 / 0 | |
| 0.8.2 | 9 / 0 | |
| 0.8.1 | 9 / 0 | |
| 0.8.0 | 9 / 0 | |
| 0.7.11 | 9 / 0 | |
| 0.7.10 | 9 / 0 | |
| 0.7.9 | 9 / 0 | |
| 0.7.8 | 9 / 0 | |
| 0.7.7 | 9 / 0 | |
| 0.7.6 | 9 / 0 | |
| 0.7.5 | 9 / 0 | |
| 0.7.4 | 9 / 0 | |
| 0.7.3 | 9 / 0 | |
| 0.7.2 | 9 / 0 | |
| 0.7.1 | 9 / 0 | |
| 0.7.0 | 9 / 0 | |
| 0.6.16 | 9 / 0 | |
| 0.6.15 | 9 / 0 | |
| 0.6.14 | 9 / 0 | |
| 0.6.13 | 9 / 0 | |
| 0.6.12 | 9 / 0 | |
| 0.6.11 | 9 / 0 | |
| 0.6.10 | 8 / 0 | |
| 0.6.9 | 8 / 0 | |
| 0.6.8 | 7 / 0 | |
| 0.6.7 | 7 / 0 | |
| 0.6.6 | 7 / 0 | |
| 0.6.5 | 7 / 0 | |
| 0.6.4 | 7 / 0 | |
| 0.6.3 | 7 / 0 | |
| 0.6.2 | 7 / 0 | |
| 0.6.1 | 7 / 0 | |
| 0.6.0 | 7 / 0 | |
| 0.5.2 | 7 / 0 | |
| 0.5.1 | 7 / 0 | |
| 0.5.0 | 7 / 0 |
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.