This ESLint plugin provides linting rules for YAML.
82%
Total Score
healthy
Regular releases and active repository work support adoption, but workflows lack pinned actions and the project has limited security coverage.
The top contributor made about 71% of the 7 recent commits, but two additional contributors were active, making this concentration a modest concern rather than a severe single-person dependency.
The project uses TypeScript, npm scripts, and Vite, but no security scanning tools were detected, leaving a modest repository-hygiene gap.
No repository security policy was found, reducing transparency about how maintainers handle vulnerability reports.
The indicator reports no type declarations, which is a consumer-facing gap for an ESLint plugin configuration API, although the published file tree includes a declaration-looking lib/index.d.mts file.
All 25 analyzed action references are unpinned, and the audit found a high-severity but low-confidence cache-poisoning pattern plus a high-confidence adhoc package install. No untrusted checkout or script injection was detected, which limits the risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@eslint/core Version ^1.0.1 | — | — |
diff-sequences Version ^29.0.0 | — | — |
natural-compare Version ^1.4.0 | — | — |
@eslint/plugin-kit Version ^0.7.0 | — | — |
yaml-eslint-parser Version ^2.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.