@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 — 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 |
|---|---|---|---|---|
| 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 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.109.52 | 11 / 0 | |
| 0.109.51 | 11 / 0 | |
| 0.109.50 | 11 / 0 | |
| 0.109.49 | 11 / 0 | |
| 0.109.48 | 11 / 0 | |
| 0.109.47 | 11 / 0 | |
| 0.109.46 | 11 / 0 | |
| 0.109.45 | 11 / 0 | |
| 0.109.44 | 11 / 0 | |
| 0.109.43 | 11 / 0 | |
| 0.109.42 | 11 / 0 | |
| 0.109.41 | 11 / 0 | |
| 0.109.40 | 11 / 0 | |
| 0.109.39 | 11 / 0 | |
| 0.109.38 | 11 / 0 | |
| 0.109.37 | 11 / 0 | |
| 0.109.36 | 11 / 0 | |
| 0.109.35 | 11 / 0 | |
| 0.109.34 | 11 / 0 | |
| 0.109.33 | 11 / 0 | |
| 0.109.32 | 11 / 0 | |
| 0.109.31 | 11 / 0 | |
| 0.109.30 | 11 / 0 | |
| 0.109.29 | 11 / 0 | |
| 0.109.28 | 11 / 0 | |
| 0.109.27 | 11 / 0 | |
| 0.109.26 | 11 / 0 | |
| 0.109.25 | 11 / 0 | |
| 0.109.24 | 11 / 0 | |
| 0.109.23 | 11 / 0 | |
| 0.109.22 | 11 / 0 | |
| 0.109.21 | 11 / 0 | |
| 0.109.20 | 11 / 0 | |
| 0.109.19 | 11 / 0 | |
| 0.109.18 | 11 / 0 | |
| 0.109.17 | 11 / 0 | |
| 0.109.16 | 11 / 0 | |
| 0.109.15 | 11 / 0 | |
| 0.109.14 | 11 / 0 | |
| 0.109.13 | 11 / 0 | |
| 0.109.12 | 11 / 0 | |
| 0.109.11 | 11 / 0 | |
| 0.109.10 | 11 / 0 | |
| 0.109.9 | 11 / 0 | |
| 0.109.8 | 11 / 0 |
v0.109.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.50
2 findingsThis version was published by a different npm account than previous versions on 2026-04-15. 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.
v0.109.49
2 findingsThis version was published by a different npm account than previous versions on 2026-04-14. 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.
v0.109.48
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. 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.
v0.109.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.46
2 findingsThis version was published by a different npm account than previous versions on 2026-04-03. 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.
v0.109.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.44
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. 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.
v0.109.43
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.
v0.109.42
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.
v0.109.41
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. 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.
v0.109.40
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. 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.
v0.109.39
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.
v0.109.38
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.
v0.109.37
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.
v0.109.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.109.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.