A TOML parser for JavaScript/TypeScript, targeting TOML 1.1.0 Spec
82%
Total Score
67
100
95
88
50
No build attestation or trusted-publisher provenance was provided, which reduces publication transparency, though it is a supply-chain transparency gap rather than evidence that the release is unsafe.
The repository is owned by an individual rather than an organization, so the single-maintainer and bus-factor concerns are not buffered by visible organizational backing.
All 47 recent commits came from one contributor, creating a meaningful continuity risk if that maintainer becomes unavailable; the active commit rate partly compensates but does not remove the concentration.
The repository uses TypeScript, Vitest, tsup, and npm scripts, demonstrating a real build and test toolchain, but no security scanning tools were detected.
No security policy was found in the repository, leaving vulnerability-reporting expectations less transparent than they could be.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-114169 js-toml is vulnerable to Regular Expression Denial of Service (ReDoS) in versions 0.0.1 - 1.2.1. | 0.0.1 - 1.2.1 | High |
CVE-2026-50029 js-toml is vulnerable to Incorrect Comparison in versions 0.0.0 - 1.1.1. | 0.0.0 - 1.1.1 | Medium |
CVE-2026-49293 js-toml is vulnerable to Uncontrolled Resource Consumption in versions 0.0.0 - 1.1.0. | 0.0.0 - 1.1.0 | High |
AIKIDO-2025-10529 js-toml is vulnerable to Prototype Pollution in versions 0.0.1 - 1.0.1. | 0.0.1 - 1.0.1 | High |
| Dependency | Last Release | Score |
|---|---|---|
xregexp Version ^5.1.2 | — | — |
chevrotain Version ^12.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.