TOML parser for Node.js (TOML v1.1.0 compliant)
78%
Total Score
75
100
94
50
50
The release has no build attestation or trusted-publisher provenance, so consumers receive less verifiable evidence about how the artifact was published.
All 14 recent commits came from one contributor, leaving maintenance capacity highly concentrated and increasing continuity risk.
The repository uses npm scripts for builds but reports no security scanning tools, leaving a security-process gap despite active development.
No repository security policy was found, reducing transparency about vulnerability reporting and response expectations.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned; the missing top-level permissions block is not concerning on its own.
| 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.