A natural language date parser in Javascript
88%
Total Score
healthy
Long-running project with six releases in the past year and active, well-distributed repository work.
A prepare script runs during installation, adding build-time behavior beyond simple file installation; this is a modest operational concern rather than a severe health issue.
The project uses TypeScript, Webpack, and npm scripts for builds, but no security-scanning tool was detected; the missing scanner is a modest transparency gap.
The repository has no security policy, leaving vulnerability-reporting expectations unclear; active commits and releases partly compensate but do not remove the documentation gap.
Both workflows were fully analyzed with no injection or high-severity findings, and no workflow has broad top-level write permissions. However, all 3 referenced actions are unpinned, which weakens CI reproducibility.
| Title | Versions | Severity |
|---|---|---|
CVE-2021-23371 chrono-node is vulnerable to Uncontrolled Resource Consumption in versions 0.0.0 - 2.2.4. | 0.0.0 - 2.2.4 | High |
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.