← Home

@morpho-org/blue-api-sdk

npm Repository Homepage

GraphQL SDK that exports types from the [API's GraphQL schema](https://blue-api.morpho.org/graphql) and a useful Apollo cache controller.

33
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

gabin53julien-devatommathisgdmerlin-egaliterubilmax

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-level automation adoption. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-automated publish with SLSA provenance; no malicious indicators in diff. ai

Versions (showing 33 of 33)

Version Deps Published
2.17.3 0 / 6
2.17.2 0 / 6
2.17.1 0 / 6
2.17.0 0 / 6
2.16.0 0 / 6
2.15.0 0 / 6
2.14.0 0 / 6
2.13.0 0 / 6
2.12.2 0 / 6
2.12.1 0 / 6
2.12.0 0 / 6
2.11.4 0 / 6
2.11.3 0 / 6
2.11.2 0 / 6
2.11.1 0 / 6
2.11.0 0 / 6
2.10.0 0 / 6
2.9.0 0 / 6
2.8.2 0 / 6
2.8.1 0 / 6
2.8.0 0 / 6
2.7.0 0 / 6
2.6.1 0 / 6
2.6.0 0 / 6
2.5.0 0 / 6
2.4.2 0 / 6
2.4.1 0 / 6
2.4.0 0 / 6
2.3.1 0 / 6
2.3.0 0 / 6
2.2.0 0 / 6
2.1.0 0 / 6
2.0.0 0 / 6

v2.6.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien-devatom → rubilmax (on 2025-04-22, known maintainer) provenance

This version was published by a different npm account (rubilmax) than the most recent previously approved version (julien-devatom) on 2025-04-22, but rubilmax 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.

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.