@graphql-inspector/similar-command
Find similar types in GraphQL Schema
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): No-diff release from long-trusted publisher; monorepo cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@graphql-inspector/logger | AI (dependencies): Internal monorepo sibling package from the same trusted publisher; not an independent risk. | ai | |
| dependencies | unvetted-dep:@graphql-inspector/commands | AI (dependencies): Internal monorepo sibling package from the same trusted publisher; not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared in dependencies and used as a runtime helper by the TypeScript compiler output; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.0.20 | 4 / 0 | |
| 5.0.19 | 4 / 0 | |
| 5.0.18 | 4 / 0 | |
| 5.0.17 | 4 / 0 | |
| 5.0.16 | 4 / 0 | |
| 5.0.15 | 4 / 0 | |
| 5.0.14 | 4 / 0 | |
| 5.0.13 | 4 / 0 | |
| 5.0.12 | 4 / 0 | |
| 5.0.11 | 4 / 0 | |
| 5.0.10 | 4 / 0 | |
| 5.0.9 | 4 / 0 | |
| 5.0.8 | 4 / 0 | |
| 5.0.7 | 4 / 0 | |
| 5.0.6 | 4 / 0 | |
| 5.0.5 | 4 / 0 | |
| 5.0.4 | 4 / 0 | |
| 5.0.0 | 4 / 0 |
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.