The linked project has recent commits, a maintained organization, clear licensing, and useful type declarations. Maintenance is concentrated in one contributor, and the repository does not explicitly mention this package; all seven workflow actions are also unpinned.
74%
Total Score
83
94
83
All 11 recent commits came from one contributor, so maintenance depends heavily on a single person. Organization ownership provides some handoff capacity but does not remove the current concentration risk.
The repository name does not match the package and its README does not mention micromark-util-types, so the package-to-repository link is less transparent than expected. The monorepo structure partly explains the name mismatch but not the absent README mention.
Both workflows were analyzed with no untrusted checkout, script injection, or high-confidence audit findings. However, all seven action references are unpinned, creating a workflow reproducibility and dependency-drift concern.
We didn't find any vulnerabilities for this package.
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.