apollo-link-set-context MIT 12 versions

apollo-link-set-context

npm Repository Homepage

Apollo Link that enables context setting

12

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

evanshauserjbaxleyiiimdg

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from evanshauser to jbaxleyiii is a documented, legitimate Apollo team transition in 2017. jbaxleyiii is a known Apollo maintainer listed as contributor in package.json.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): jbaxleyiii (James Baxley) is a well-established Apollo team member with 1064 approved packages and is listed as a contributor. This is a legitimate maintainer addition.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is a deliberate versioning choice for early Apollo monorepo packages; package is 3195 days old with 14 versions and a legitimate publisher history.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
0.5.4	1 / 18	2017-09-07
0.5.2	1 / 19	2017-09-07
0.5.0	1 / 18	2017-08-09
0.4.1	1 / 18	2017-08-09
0.4.0	1 / 18	2017-08-09
0.3.1	1 / 18	2017-08-08
0.3.0	1 / 18	2017-08-08
0.2.0	1 / 19	2017-07-29
0.1.1	1 / 19	2017-07-28
0.1.0	1 / 19	2017-07-28
0.0.1	1 / 19	2017-07-25
0.0.0	1 / 19	2017-07-25

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.2

2 findings

HIGH Publisher changed: evanshauser → jbaxleyiii (on 2017-09-07) provenance

This version was published by a different npm account than previous versions on 2017-09-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.1

1 finding

LOW No provenance attestation provenance

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

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