apollo-link-http MIT 26 versions

apollo-link-http

npm Repository Homepage

HTTP transport layer for GraphQL

26

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

apollo-botevanshauserjbaxleyiii

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Historical org transfer to apollo-bot, long-stable, not a fresh takeover signal.	ai	2026/07/19
maintainer-change	maintainer-removed	AI (maintainer-change): Same historical transfer, not indicative of compromise.	ai	2026/07/19
provenance	publisher-changed-stale	AI (provenance): Publisher change is old and stale per analyzer's own framing; not a takeover.	ai	2026/07/19

Versions (showing 26 of 26)

Version	Deps	Published
1.5.17	3 / 13	2020-04-09
1.5.16	3 / 13	2019-09-06
1.5.15	3 / 13	2019-06-14
1.5.14	3 / 13	2019-03-14
1.5.13	3 / 13	2019-03-14
1.5.12	3 / 13	2019-03-05
1.5.11	2 / 15	2019-02-01
1.5.10	2 / 15	2019-02-01
1.5.9	2 / 15	2018-12-15
1.5.8	2 / 15	2018-12-13
1.5.7	2 / 15	2018-11-22
1.5.6	2 / 15	2018-11-21
1.5.5	2 / 15	2018-09-15
1.5.4	2 / 15	2018-04-12
1.5.3	2 / 15	2018-03-05
1.5.2	2 / 15	2018-02-27
1.5.1	2 / 15	2018-02-23
1.5.0	2 / 15	2018-02-22
1.4.0	2 / 15	2018-02-21
1.3.3	1 / 15	2018-02-08
1.3.2	1 / 15	2017-12-18
1.3.1	1 / 15	2017-12-08
1.3.0	1 / 15	2017-11-30
1.2.0	0 / 15	2017-11-15
1.1.0	0 / 15	2017-11-01
1.0.0	0 / 15	2017-10-24

v1.5.15

1 finding

LOW No provenance attestation provenance

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

v1.5.13

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2019-03-14, unremoved on npm for 2684d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2019-03-14. It has since remained available on npm for 2684 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.12

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2019-03-05, unremoved on npm for 2692d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2019-03-05. It has since remained available on npm for 2692 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.11

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2019-02-01, unremoved on npm for 2724d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2019-02-01. It has since remained available on npm for 2724 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.10

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2019-02-01, unremoved on npm for 2725d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2019-02-01. It has since remained available on npm for 2725 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.9

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2018-12-15, unremoved on npm for 2773d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2018-12-15. It has since remained available on npm for 2773 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.8

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2018-12-13, unremoved on npm for 2774d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2018-12-13. It has since remained available on npm for 2774 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.7

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2018-11-22, unremoved on npm for 2796d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2018-11-22. It has since remained available on npm for 2796 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.6

2 findings

MEDIUM Publisher changed: mdg → apollo-bot (on 2018-11-21, unremoved on npm for 2797d) provenance

This version was published by a different npm account (apollo-bot) than the most recent previously approved version (mdg) on 2018-11-21. It has since remained available on npm for 2797 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.5.5

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: evanshauser → mdg (on 2018-09-15, known maintainer) provenance

This version was published by a different npm account (mdg) than the most recent previously approved version (evanshauser) on 2018-09-15, 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.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

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: evanshauser → jbaxleyiii (on 2018-02-27, known maintainer) provenance

This version was published by a different npm account (jbaxleyiii) than the most recent previously approved version (evanshauser) on 2018-02-27, 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.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.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: mdg → evanshauser (on 2018-02-21, known maintainer) provenance

This version was published by a different npm account (evanshauser) than the most recent previously approved version (mdg) on 2018-02-21, but evanshauser 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.3.3

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: mdg → jbaxleyiii (on 2018-02-08, known maintainer) provenance

This version was published by a different npm account (jbaxleyiii) than the most recent previously approved version (mdg) on 2018-02-08, 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.3.2

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: jbaxleyiii → mdg (on 2017-12-18, known maintainer) provenance

This version was published by a different npm account (mdg) than the most recent previously approved version (jbaxleyiii) on 2017-12-18, 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.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.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.

v1.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.