Lint your commit messages
84%
Total Score
100
100
89
67
The repository name does not match the package and its README does not mention it, so the package-to-repository relationship is less transparent despite the apparent monorepo context.
The project uses TypeScript, Vitest, and build tooling, but no security-scanning tools were detected, leaving a modest transparency gap.
No repository security policy was detected. This is a documentation gap, though the active organization-backed project provides some compensating maintenance evidence.
All five workflows were analyzed with no untrusted checkout or script-injection findings, but 20 of 25 action references are unpinned and CI installs a package outside a lockfile; these are workflow hygiene concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
semver Version ^7.6.0 | — | — |
@commitlint/types Version ^21.2.3 | — | — |
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.