graphile-test
PostGraphile Testing
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@launchql/env | AI (phantom-deps): Config-only reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@launchql/types | AI (phantom-deps): @launchql/types is a declared runtime dep from the same org; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:mock-req | AI (phantom-deps): Declared in deps; likely used transitively or in test helpers, not a security concern. | ai | |
| phantom-deps | phantom-dep:@pgpmjs/types | AI (phantom-deps): Types-only package; phantom-dep false positive common for type-only imports. | ai | |
| phantom-deps | phantom-dep:@constructive-io/graphql-env | AI (phantom-deps): Internal org package; likely re-exported or used indirectly, stable false positive. | ai | |
| phantom-deps | phantom-dep:@constructive-io/graphql-types | AI (phantom-deps): Internal org types package; phantom-dep heuristic unreliable for type-only usage. | ai |
Versions (showing 100 of 170)
| Version | Deps | Published |
|---|---|---|
| 4.17.4 | 12 / 3 | |
| 4.17.3 | 12 / 3 | |
| 4.17.2 | 12 / 3 | |
| 4.17.1 | 12 / 3 | |
| 4.17.0 | 12 / 3 | |
| 4.16.2 | 12 / 3 | |
| 4.16.1 | 12 / 3 | |
| 4.16.0 | 12 / 3 | |
| 4.15.3 | 12 / 3 | |
| 4.15.2 | 12 / 3 | |
| 4.15.1 | 12 / 3 | |
| 4.15.0 | 12 / 3 | |
| 4.14.2 | 12 / 3 | |
| 4.14.1 | 12 / 3 | |
| 4.14.0 | 12 / 3 | |
| 4.13.0 | 12 / 3 | |
| 4.12.1 | 12 / 3 | |
| 4.12.0 | 12 / 3 | |
| 4.11.0 | 12 / 3 | |
| 4.10.0 | 12 / 3 | |
| 4.9.5 | 12 / 3 | |
| 4.9.4 | 12 / 3 | |
| 4.9.3 | 12 / 3 | |
| 4.9.2 | 12 / 3 | |
| 4.9.1 | 12 / 3 | |
| 4.9.0 | 12 / 3 | |
| 4.8.1 | 12 / 3 | |
| 4.8.0 | 12 / 3 | |
| 4.7.8 | 12 / 3 | |
| 4.7.7 | 12 / 3 | |
| 4.7.6 | 12 / 3 | |
| 4.7.5 | 12 / 3 | |
| 4.7.4 | 12 / 3 | |
| 4.7.3 | 12 / 3 | |
| 4.7.2 | 12 / 3 | |
| 4.7.1 | 12 / 3 | |
| 4.7.0 | 12 / 3 | |
| 4.6.3 | 12 / 3 | |
| 4.6.1 | 12 / 3 | |
| 4.6.0 | 12 / 3 | |
| 4.5.10 | 12 / 3 | |
| 4.5.9 | 12 / 3 | |
| 4.5.8 | 12 / 3 | |
| 4.5.7 | 12 / 3 | |
| 4.5.6 | 12 / 3 | |
| 4.5.5 | 12 / 3 | |
| 4.5.4 | 12 / 3 | |
| 4.5.3 | 12 / 3 | |
| 4.5.2 | 12 / 3 | |
| 4.3.2 | 12 / 3 | |
| 4.3.1 | 12 / 3 | |
| 4.3.0 | 12 / 3 | |
| 4.2.4 | 12 / 3 | |
| 4.2.3 | 12 / 3 | |
| 4.2.2 | 12 / 3 | |
| 4.2.1 | 12 / 3 | |
| 4.2.0 | 12 / 3 | |
| 4.1.1 | 12 / 3 | |
| 4.1.0 | 12 / 3 | |
| 4.0.0 | 12 / 3 | |
| 3.1.1 | 8 / 3 | |
| 3.1.0 | 8 / 3 | |
| 3.0.4 | 8 / 3 | |
| 3.0.3 | 8 / 3 | |
| 3.0.2 | 8 / 3 | |
| 3.0.1 | 8 / 3 | |
| 3.0.0 | 8 / 3 | |
| 2.15.4 | 8 / 3 | |
| 2.15.3 | 8 / 3 | |
| 2.15.2 | 8 / 3 | |
| 2.15.1 | 8 / 3 | |
| 2.15.0 | 8 / 3 | |
| 2.14.1 | 8 / 3 | |
| 2.14.0 | 8 / 3 | |
| 2.13.16 | 8 / 3 | |
| 2.13.15 | 8 / 3 | |
| 2.13.14 | 8 / 3 | |
| 2.13.13 | 8 / 3 | |
| 2.13.12 | 8 / 3 | |
| 2.13.11 | 8 / 3 | |
| 2.13.10 | 8 / 3 | |
| 2.13.9 | 8 / 3 | |
| 2.13.8 | 8 / 3 | |
| 2.13.7 | 8 / 3 | |
| 2.13.6 | 8 / 3 | |
| 2.13.5 | 8 / 3 | |
| 2.13.4 | 8 / 3 | |
| 2.13.3 | 8 / 3 | |
| 2.13.2 | 8 / 3 | |
| 2.13.1 | 8 / 3 | |
| 2.13.0 | 8 / 3 | |
| 2.12.0 | 8 / 3 | |
| 2.11.42 | 8 / 3 | |
| 2.11.41 | 8 / 3 | |
| 2.11.40 | 8 / 3 | |
| 2.11.39 | 8 / 3 | |
| 2.11.38 | 8 / 3 | |
| 2.11.37 | 8 / 3 | |
| 2.11.36 | 8 / 3 | |
| 2.11.35 | 8 / 3 |
v4.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
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.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.