TOML parser for Node.js (TOML v1.1.0 compliant)
79%
Total Score
healthy
Frequent releases and recent commits support a healthy package, despite one-person maintenance and unpinned workflow actions.
The repository is owned by an individual user rather than an organization, so the single-contributor maintenance concentration is not offset by visible organizational backing.
All 9 recent commits came from one contributor, leaving maintenance continuity dependent on a single person.
The project uses npm build tooling, but no security-scanning tool was detected; this is a modest transparency gap rather than evidence of unsafe code.
The repository has no security policy, reducing clarity about vulnerability reporting and response expectations.
The workflow audit completed cleanly with no injection or high-severity findings, but both of its two action references are unpinned, weakening build reproducibility.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-63376 toml is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in versions 0.0.0 - 4.1.2. | 0.0.0 - 4.1.2 | High |
AIKIDO-2026-158991 toml is vulnerable to Uncontrolled Recursion in versions 0.0.1 - 4.1.2. | 0.0.1 - 4.1.2 | 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.