A small, fast, and correct TOML parser/serializer
88%
Total Score
healthy
Active releases, verified publishing, and controlled CI outweigh the repository's concentrated maintenance and security-documentation gaps.
Only one account has registry publish access, which is a modest publishing resilience concern. The repository is organization-owned, so this is less concerning than a wholly unsupported single-person project.
Commit activity is highly concentrated: one contributor made 39 of 40 recent commits. The organization-owned repository and a second active contributor partly compensate, but succession resilience remains limited.
The project uses a build toolchain including TypeScript, Rolldown, and Vite, but no security scanning tools were detected. The build setup is healthy; the missing scanning is a minor transparency gap.
No repository security policy was found. This does not show unsafe code, but it reduces transparency about how vulnerability reports are handled.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-430108 smol-toml is vulnerable to Denial of Service (DoS) in versions 0.0.1 - 1.8.0. | 0.0.1 - 1.8.0 | Medium |
AIKIDO-2026-768164 smol-toml is vulnerable to Denial of Service (DoS) in versions 1.0.1 - 1.7.0. | 1.0.1 - 1.7.0 | High |
AIKIDO-2025-10243 smol-toml is vulnerable to Uncontrolled Recursion in versions 1.0.0 - 1.3.2. | 1.0.0 - 1.3.2 | Low |
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.