@omnigraph/json-schema
This package generates GraphQL Schema from JSON Schema and sample JSON request and responses. You can define your root field endpoints like below in your GraphQL Config for example;
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 publishing is confirmed by SLSA Sigstore attestation; legitimate automation handoff for this established package. | ai | |
| dependencies | unvetted-dep:graphql-fields | AI (dependencies): Long-standing declared dep in this package; phantom-dep finding already accepted, stable pattern. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/transport-rest | AI (dependencies): First-party @graphql-mesh ecosystem dep; consistent across versions. | ai | |
| dependencies | unvetted-dep:@graphql-mesh/transport-common | AI (dependencies): First-party @graphql-mesh ecosystem dep; consistent across versions. | ai | |
| phantom-deps | phantom-dep:dset | AI (phantom-deps): Listed in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:url-join | AI (phantom-deps): Listed in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql-fields | AI (phantom-deps): Listed in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/delegate | AI (phantom-deps): Listed in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 27 of 127)
| Version | Deps | Published |
|---|---|---|
| 0.101.2 | 17 / 0 | |
| 0.101.1 | 17 / 0 | |
| 0.101.0 | 17 / 0 | |
| 0.100.13 | 17 / 0 | |
| 0.100.12 | 17 / 0 | |
| 0.100.11 | 17 / 0 | |
| 0.100.10 | 17 / 0 | |
| 0.100.9 | 17 / 0 | |
| 0.100.8 | 17 / 0 | |
| 0.100.7 | 17 / 0 | |
| 0.100.6 | 17 / 0 | |
| 0.100.5 | 17 / 0 | |
| 0.100.4 | 17 / 0 | |
| 0.100.3 | 17 / 0 | |
| 0.100.2 | 17 / 0 | |
| 0.100.1 | 17 / 0 | |
| 0.100.0 | 17 / 0 | |
| 0.99.6 | 17 / 0 | |
| 0.99.5 | 17 / 0 | |
| 0.99.4 | 17 / 0 | |
| 0.99.3 | 17 / 0 | |
| 0.99.2 | 17 / 0 | |
| 0.99.1 | 17 / 0 | |
| 0.99.0 | 17 / 0 | |
| 0.98.2 | 17 / 0 | |
| 0.98.1 | 17 / 0 | |
| 0.98.0 | 17 / 0 |
v0.101.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.