apollo-utilities
Utilities for working with GraphQL ASTs
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata gap from older publish tooling, not a behavioral change; consistent across this package's history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): apollo-bot is the Apollo organization's official publishing bot; this transition is expected and documented across the apollographql ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mdg (Meteor Development Group) removal is part of the known Apollo org transition to apollographql; stable organizational change, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): The benjamn → apollo-bot transition is a well-documented, legitimate move by the Apollo team to a shared bot account for automated publishing; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice signal but not a security blocker; apollo-bot's long track record and 448 approved packages provide sufficient trust. | ai | |
| dependencies | unvetted-dep:lodash.isequal | AI (dependencies): lodash.isequal is a well-known, widely-used utility from the lodash ecosystem; its use in apollo-utilities for deep equality checks is legitimate and expected. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fclone is a legitimate, established deep-clone utility appropriate for GraphQL AST manipulation; not a supply-chain attack vector. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by release is expected for stable utility libraries undergoing dependency maintenance, not indicative of account takeover. | ai | |
| dependencies | unvetted-dep:fast-json-stable-stringify | AI (dependencies): Already accepted in prior versions; stable dependency for JSON serialization in GraphQL utilities. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 4 / 0 | |
| 1.3.3 | 4 / 0 | |
| 1.3.2 | 4 / 0 | |
| 1.3.1 | 4 / 1 | |
| 1.3.0 | 3 / 0 | |
| 1.2.1 | 3 / 0 | |
| 1.2.0 | 3 / 0 | |
| 1.1.3 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.27 | 1 / 0 | |
| 1.0.26 | 1 / 0 | |
| 1.0.25 | 1 / 0 | |
| 1.0.24 | 1 / 0 | |
| 1.0.23 | 1 / 0 | |
| 1.0.22 | 1 / 0 | |
| 1.0.21 | 2 / 0 | |
| 1.0.20 | 1 / 0 | |
| 1.0.19 | 1 / 16 | |
| 1.0.18 | 1 / 16 | |
| 1.0.17 | 1 / 16 | |
| 1.0.16 | 1 / 16 | |
| 1.0.15 | 1 / 16 | |
| 1.0.14 | 1 / 16 | |
| 1.0.13 | 0 / 16 | |
| 1.0.12 | 0 / 16 | |
| 1.0.11 | 0 / 16 | |
| 1.0.10 | 0 / 16 | |
| 1.0.9 | 0 / 16 | |
| 1.0.8 | 0 / 16 | |
| 1.0.7 | 0 / 16 | |
| 1.0.6 | 0 / 16 | |
| 1.0.5 | 0 / 16 | |
| 1.0.4 | 0 / 16 | |
| 1.0.3 | 0 / 16 | |
| 1.0.2 | 0 / 16 | |
| 1.0.1 | 0 / 15 | |
| 1.0.0 | 0 / 15 |
v1.0.23
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: benjamn.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mdg) than the most recent previously approved version (hwillson) on 2018-06-13, but mdg 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.
v1.0.13
2 findingsThis version was published by a different npm account (hwillson) than the most recent previously approved version (benjamn) on 2018-05-30. It has since remained available on npm for 2978 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
2 findingsThis version was published by a different npm account (benjamn) than the most recent previously approved version (jbaxleyiii) on 2018-05-02. It has since remained available on npm for 3005 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jbaxleyiii) than the most recent previously approved version (peggyrayzis) on 2018-03-26, but jbaxleyiii 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.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (peggyrayzis) than the most recent previously approved version (jbaxleyiii) on 2018-02-14, but peggyrayzis 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.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.