@constructive-io/react
Constructive React - Auto-generated React Query hooks and ORM client
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@constructive-io/graphql-types | AI (phantom-deps): Same-org dep; likely re-exported via another dep rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@0no-co/graphql.web | AI (phantom-deps): Referenced in config/type declarations; stable false positive for this package. | ai |
Versions (showing 95 of 196)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 6 / 7 | |
| 0.15.4 | 6 / 7 | |
| 0.15.3 | 6 / 7 | |
| 0.15.2 | 6 / 7 | |
| 0.15.1 | 6 / 7 | |
| 0.15.0 | 6 / 7 | |
| 0.14.2 | 6 / 7 | |
| 0.14.1 | 6 / 7 | |
| 0.14.0 | 6 / 7 | |
| 0.13.1 | 6 / 7 | |
| 0.13.0 | 6 / 7 | |
| 0.12.12 | 6 / 7 | |
| 0.12.11 | 5 / 7 | |
| 0.12.10 | 5 / 7 | |
| 0.12.9 | 5 / 7 | |
| 0.12.8 | 5 / 7 | |
| 0.12.7 | 5 / 7 | |
| 0.12.6 | 5 / 7 | |
| 0.12.5 | 5 / 7 | |
| 0.12.4 | 5 / 7 | |
| 0.12.3 | 5 / 7 | |
| 0.12.2 | 5 / 7 | |
| 0.12.1 | 5 / 7 | |
| 0.12.0 | 5 / 7 | |
| 0.11.4 | 5 / 7 | |
| 0.11.3 | 5 / 7 | |
| 0.11.2 | 5 / 7 | |
| 0.11.1 | 5 / 7 | |
| 0.11.0 | 5 / 7 | |
| 0.10.23 | 5 / 7 | |
| 0.10.22 | 5 / 7 | |
| 0.10.21 | 5 / 7 | |
| 0.10.20 | 5 / 7 | |
| 0.10.19 | 5 / 7 | |
| 0.10.18 | 5 / 7 | |
| 0.10.17 | 5 / 7 | |
| 0.10.16 | 5 / 7 | |
| 0.10.15 | 5 / 7 | |
| 0.10.14 | 5 / 7 | |
| 0.10.13 | 5 / 7 | |
| 0.10.12 | 5 / 7 | |
| 0.10.11 | 5 / 7 | |
| 0.10.10 | 5 / 7 | |
| 0.10.9 | 5 / 7 | |
| 0.10.8 | 5 / 7 | |
| 0.10.7 | 5 / 7 | |
| 0.10.6 | 5 / 7 | |
| 0.10.5 | 5 / 7 | |
| 0.10.4 | 5 / 7 | |
| 0.10.3 | 5 / 7 | |
| 0.10.1 | 5 / 7 | |
| 0.10.0 | 5 / 7 | |
| 0.9.8 | 5 / 7 | |
| 0.9.7 | 5 / 7 | |
| 0.9.6 | 5 / 7 | |
| 0.9.5 | 5 / 7 | |
| 0.9.2 | 5 / 7 | |
| 0.9.1 | 5 / 7 | |
| 0.9.0 | 5 / 7 | |
| 0.8.5 | 5 / 7 | |
| 0.8.4 | 5 / 7 | |
| 0.8.3 | 5 / 7 | |
| 0.8.2 | 5 / 7 | |
| 0.8.1 | 5 / 7 | |
| 0.8.0 | 5 / 7 | |
| 0.7.2 | 5 / 7 | |
| 0.7.1 | 5 / 7 | |
| 0.7.0 | 5 / 7 | |
| 0.6.14 | 5 / 7 | |
| 0.6.13 | 5 / 7 | |
| 0.6.12 | 5 / 7 | |
| 0.6.11 | 5 / 7 | |
| 0.6.10 | 5 / 7 | |
| 0.6.9 | 5 / 7 | |
| 0.6.8 | 5 / 7 | |
| 0.6.7 | 5 / 7 | |
| 0.6.6 | 5 / 7 | |
| 0.6.5 | 5 / 7 | |
| 0.6.4 | 5 / 7 | |
| 0.6.3 | 5 / 7 | |
| 0.6.2 | 5 / 7 | |
| 0.6.1 | 5 / 7 | |
| 0.6.0 | 5 / 7 | |
| 0.5.4 | 5 / 7 | |
| 0.5.3 | 5 / 7 | |
| 0.5.2 | 5 / 7 | |
| 0.3.2 | 5 / 7 | |
| 0.3.1 | 5 / 7 | |
| 0.3.0 | 5 / 7 | |
| 0.2.3 | 5 / 7 | |
| 0.2.2 | 5 / 7 | |
| 0.2.1 | 5 / 7 | |
| 0.2.0 | 5 / 7 | |
| 0.1.1 | 5 / 7 | |
| 0.1.0 | 5 / 7 |
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.