Apollo Federation internal utilities
76%
Total Score
healthy
Healthy with caveats: frequent releases and active organization backing outweigh workflow and package-identity hygiene concerns.
The repository name does not match the package and its README does not mention @apollo/federation-internals. This is plausible for a monorepo but leaves the package-to-source relationship less explicit.
The repository uses TypeScript and npm build tooling, but no security scanning tools were detected. This is a modest repository-hygiene gap rather than evidence of abandonment.
The single analyzed workflow grants top-level write permissions, uses all three actions without pinning, and has two high-confidence template-injection findings. No untrusted checkout or script-injection sink was detected, so these remain workflow-hygiene concerns rather than a standalone severe risk.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-32621 @apollo/federation-internals is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 0.0.0 - 2.9.6, 2.10.0 - 2.10.5, 2.11.0 - 2.11.6, 2.12.0 - 2.12.3 and 2.13.0 - 2.13.2. | 0.0.0 - 2.9.62.10.0 - 2.10.52.11.0 - 2.11.6 +2 more | Critical |
| Dependency | Last Release | Score |
|---|---|---|
uuid Version ^9.0.0 | — | — |
chalk Version ^4.1.0 | — | — |
@types/uuid Version ^9.0.0 | — | — |
js-levenshtein Version ^1.1.6 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.