Check what’s defined in an estree scope
82%
Total Score
100
100
89
88
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. This is a transparency gap but not evidence that the release is unsafe.
Only two releases exist across roughly two years, with one release in the last 12 months and a median interval of about 726 days. Recent repository activity partly offsets the sparse release cadence, but the history provides limited maturity evidence.
The project uses TypeScript and npm build tooling, but no security-scanning tool was detected. For this small library, the missing scanner is a minor hygiene gap rather than a maintenance failure.
Both workflows were analyzed with no audit findings, no untrusted checkout or script-injection paths, and no top-level write permissions. However, all four action references are unpinned, which weakens build reproducibility and warrants a modest caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
devlop Version ^1.0.0 | — | — |
@types/estree Version ^1.0.0 | — | — |
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.