apollo-link-polling
Polling Apollo Link for GraphQL Network Stack
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the established initial version pattern for Apollo Link monorepo packages; package is ~9 years old with 21 versions and a legitimate publisher. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from evanshauser to jbaxleyiii reflects a legitimate Apollo org transition; both are listed in package.json and the repo is under apollographql org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jbaxleyiii (James Baxley) is a contributor listed in package.json and a well-established publisher in the Apollo ecosystem; addition is legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2017, before Sigstore provenance was available. No provenance is expected for packages of this age. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 14 | |
| 0.8.0 | 0 / 14 | |
| 0.7.0 | 0 / 13 | |
| 0.5.4 | 1 / 18 | |
| 0.5.2 | 1 / 19 | |
| 0.5.0 | 1 / 18 | |
| 0.4.1 | 1 / 18 | |
| 0.4.0 | 1 / 18 | |
| 0.3.1 | 1 / 18 | |
| 0.3.0 | 1 / 18 | |
| 0.2.0 | 1 / 19 | |
| 0.1.1 | 1 / 19 | |
| 0.1.0 | 1 / 19 | |
| 0.0.1 | 1 / 19 | |
| 0.0.0 | 1 / 19 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.