@constructive-io/graphql-query
Constructive GraphQL Query
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): inflekt is a benign string inflection library; publisher has strong track record with no rejections. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Legitimate package expansion with new GraphQL/PostGraphile integration code; trusted publisher with clean track record. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase attributable to added PostGraphile/grafast integration modules; no obfuscation or payload indicators. | ai | |
| phantom-deps | phantom-dep:inflection | AI (phantom-deps): inflection is a declared dep used indirectly via graphile ecosystem; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphile-config | AI (phantom-deps): graphile-config referenced in config files as expected for graphile ecosystem integration; stable false positive. | ai |
Versions (showing 27 of 131)
| Version | Deps | Published |
|---|---|---|
| 3.5.3 | 11 / 1 | |
| 3.5.2 | 11 / 1 | |
| 3.3.4 | 11 / 1 | |
| 3.3.3 | 11 / 1 | |
| 3.3.2 | 11 / 1 | |
| 3.3.1 | 11 / 1 | |
| 3.3.0 | 11 / 1 | |
| 3.2.5 | 10 / 1 | |
| 3.2.4 | 10 / 1 | |
| 3.2.3 | 10 / 1 | |
| 3.2.2 | 10 / 1 | |
| 3.2.1 | 10 / 1 | |
| 3.2.0 | 10 / 1 | |
| 3.1.1 | 10 / 1 | |
| 3.1.0 | 10 / 1 | |
| 3.0.1 | 10 / 1 | |
| 3.0.0 | 10 / 1 | |
| 2.8.0 | 4 / 1 | |
| 2.7.0 | 4 / 1 | |
| 2.6.0 | 4 / 1 | |
| 2.5.1 | 4 / 1 | |
| 2.5.0 | 4 / 1 | |
| 2.4.7 | 4 / 1 | |
| 2.4.6 | 4 / 1 | |
| 2.4.5 | 5 / 1 | |
| 2.4.4 | 5 / 1 | |
| 2.4.3 | 5 / 1 |
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.