@graphql-inspector/action
GraphQL Inspector functionality for GitHub Actions
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding GitHub blob API content (base64-encoded by GitHub) — standard pattern for this action. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Git operations in a GitHub Action context; expected and documented behavior. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): User-configured usage hook loaded via dynamic require; intentional plugin pattern. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy handler for token-count validation; not obfuscation. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.0.20 | 8 / 0 | |
| 5.0.19 | 8 / 0 | |
| 5.0.18 | 8 / 0 | |
| 5.0.17 | 8 / 0 | |
| 5.0.16 | 8 / 0 | |
| 5.0.15 | 8 / 0 | |
| 5.0.14 | 8 / 0 | |
| 5.0.13 | 8 / 0 | |
| 5.0.12 | 8 / 0 | |
| 5.0.11 | 8 / 0 | |
| 5.0.10 | 8 / 0 | |
| 5.0.9 | 8 / 0 | |
| 5.0.8 | 8 / 0 | |
| 5.0.7 | 8 / 0 | |
| 5.0.6 | 8 / 0 | |
| 5.0.5 | 8 / 0 | |
| 5.0.4 | 8 / 0 | |
| 5.0.0 | 8 / 0 |
v5.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.