Get the dependencies of a TypeScript module
82%
Total Score
83
100
94
75
50
No build attestation or trusted-publisher provenance is present, so consumers cannot verify how this release was produced. This is a transparency weakness, not evidence of maliciousness.
One contributor made all 5 commits in the last 3 months, creating concentration risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository has no security policy, which reduces transparency about vulnerability reporting and response expectations.
No type declarations are published. This is a minor integration gap for consumers using TypeScript, but the package has clear usage documentation and exposes a focused API.
All three workflows use read-only permissions and the audit found no high- or medium-severity findings, but all 7 analyzed action references are unpinned, leaving workflow dependencies exposed to tag changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ast-module-types Version ^7.0.0 | — | — |
node-source-walk Version ^8.0.0 | — | — |
@typescript-eslint/typescript-estree Version ^8.62.1 | — | — |
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.