@stonecrop/graphql-client
GraphQL client integration for Stonecrop
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@stonecrop/stonecrop | AI (phantom-deps): Same-org monorepo sibling; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): GraphQL is a peer/config-level dependency in a GraphQL client package; stable false positive. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): Declared dep referenced in config files; stable false positive for this package. | ai |
Versions (showing 51 of 96)
| Version | Deps | Published |
|---|---|---|
| 0.13.7 | 4 / 16 | |
| 0.13.6 | 4 / 16 | |
| 0.13.5 | 4 / 16 | |
| 0.13.4 | 4 / 20 | |
| 0.13.3 | 4 / 20 | |
| 0.13.2 | 4 / 20 | |
| 0.13.1 | 4 / 20 | |
| 0.12.8 | 4 / 20 | |
| 0.12.7 | 4 / 20 | |
| 0.12.6 | 4 / 20 | |
| 0.12.5 | 4 / 20 | |
| 0.12.4 | 4 / 20 | |
| 0.12.3 | 4 / 20 | |
| 0.12.2 | 4 / 20 | |
| 0.12.1 | 4 / 20 | |
| 0.12.0 | 4 / 20 | |
| 0.11.10 | 4 / 20 | |
| 0.11.9 | 4 / 20 | |
| 0.11.8 | 4 / 20 | |
| 0.11.7 | 4 / 20 | |
| 0.11.6 | 4 / 20 | |
| 0.11.5 | 4 / 20 | |
| 0.10.16 | 5 / 18 | |
| 0.10.15 | 5 / 18 | |
| 0.10.14 | 5 / 18 | |
| 0.10.13 | 5 / 18 | |
| 0.10.12 | 5 / 18 | |
| 0.10.11 | 5 / 18 | |
| 0.10.10 | 5 / 18 | |
| 0.10.9 | 5 / 18 | |
| 0.10.8 | 5 / 18 | |
| 0.10.7 | 5 / 18 | |
| 0.10.6 | 5 / 18 | |
| 0.10.5 | 5 / 18 | |
| 0.10.4 | 5 / 18 | |
| 0.10.3 | 5 / 18 | |
| 0.10.2 | 5 / 18 | |
| 0.10.1 | 5 / 18 | |
| 0.10.0 | 5 / 18 | |
| 0.9.2 | 5 / 18 | |
| 0.9.1 | 5 / 18 | |
| 0.9.0 | 5 / 18 | |
| 0.8.13 | 5 / 18 | |
| 0.8.12 | 5 / 18 | |
| 0.8.11 | 5 / 18 | |
| 0.8.10 | 4 / 16 | |
| 0.8.9 | 4 / 16 | |
| 0.8.8 | 4 / 16 | |
| 0.8.7 | 4 / 16 | |
| 0.8.6 | 4 / 16 | |
| 0.8.5 | 4 / 16 |
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alchez) than the most recent previously approved version (knuckledown) on 2026-05-28, but alchez is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alchez) than the most recent previously approved version (knuckledown) on 2026-05-28, but alchez is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.