Tooling to test ESLint rules
92%
Total Score
healthy
Frequent releases, active project backing, provenance, and a maintained repository make this a strong dependency choice.
The repository name does not match this subpackage and its README does not mention the package, creating some uncertainty about package-to-repository correspondence; the organization-backed monorepo context partly offsets that concern.
The project uses TypeScript, Vitest, Nx, Vite, SWC, and npm scripts, demonstrating a structured build and test setup. No security scanning tools were detected, a minor hygiene gap.
All 15 workflows were analyzed with no failed files, all 37 action references are pinned, and 13 workflows use read-only permissions. Two high-confidence low-severity adhoc-package findings install packages outside a lockfile, which is a limited release-hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ajv Version ^6.12.6 | — | — |
semver Version ^7.7.3 | — | — |
lodash.merge Version 4.6.2 | — | — |
@typescript-eslint/utils Version 8.71.1 | — | — |
@typescript-eslint/parser Version 8.71.1 | — | — |
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.