Remove aliases from a GraphQL document
62%
Total Score
75
100
81
83
50
No build attestation or trusted-publisher provenance is present. This limits publication transparency, though it is a supply-chain assurance gap rather than evidence that the package is unsafe to depend on.
The latest release was over three years ago, with no releases in the last 12 months. This is a meaningful maintenance concern for a dependency, despite the package having four releases and a stable release history overall.
The repository recorded zero commits and zero active maintainers in the last three months. That indicates currently inactive maintenance, although inactivity alone does not prove abandonment.
The linked repository name does not match the package name and its README does not mention this package. Because this is a subpackage in an organization repository, the name mismatch is explainable, but the lack of a README mention still reduces package-to-repository transparency.
The repository uses TypeScript and npm build tooling, but no security scanning tools were detected. The build setup is clear, while security-process visibility is limited.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.