@makerx/graphql-core
A set of core GraphQL utilities that MakerX uses to build GraphQL APIs
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package now publishes via GitHub Actions CI with SLSA attestation; this is the expected pattern for MakerX org packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer addition aligns with org-level CI publishing transition; no malicious indicators present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established org package with real repo and downloads; README style reflects internal utility docs, not a link farm. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 0 / 0 | |
| 3.1.0 | 0 / 0 | |
| 3.0.1 | 0 / 0 | |
| 3.0.0 | 0 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.2 | 1 / 0 | |
| 2.2.1 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.0 | 3 / 0 |
v3.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.