@apollographql/graphql-upload-8-fork
Fork of graphql-upload@8 that works with graphql@15 for compatibility with apollo-server@2
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
Keywords
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 apollo-bot to glasser reflects a legitimate Apollo team transition; glasser is a known Apollo engineer with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): glasser and trevor.scheer are known Apollo GraphQL engineers; addition is consistent with legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of older maintainers is consistent with Apollo team restructuring, not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): This is a legacy compatibility fork for apollo-server@2; long dormancy is expected and the publish is by a trusted Apollo engineer. | ai | |
| phantom-deps | phantom-dep:@types/koa | AI (phantom-deps): @types/koa is a TypeScript type declaration included as a runtime dep for consumers; not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a TypeScript type declaration included as a runtime dep for consumers; not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/fs-capacitor | AI (phantom-deps): @types/fs-capacitor is a TypeScript type declaration included as a runtime dep for consumers; not a security concern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.1.4 | 7 / 22 | |
| 8.1.3 | 7 / 22 | |
| 8.1.2 | 4 / 22 | |
| 8.1.1 | 4 / 22 |
v8.1.4
2 findingsThis version was published by a different npm account than previous versions on 2022-10-20. 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.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.