React Doctor rules for oxlint.
82%
Total Score
healthy
Active, well-supported project, but the package link to its repository is unclear and release/workflow hygiene is uneven.
The repository name does not match the package name and its README does not mention this package, so the package-to-repository link is not directly established. A monorepo can explain a name mismatch, but the missing README mention remains a transparency concern.
The project uses TypeScript, Vite, Turbo, and npm scripts, showing a structured build process. No security-scanning tools were detected, leaving a modest transparency and hygiene gap.
The repository has no security policy. That does not show an immediate dependency failure, but it weakens the project's documented process for receiving and handling vulnerabilities.
Version 0.9.18 is not a stable major and 95% of recent releases are prereleases, so the API may still change frequently. That is a meaningful maturity concern, though the assessed version itself is not marked prerelease.
All eight workflows were analyzed with no untrusted checkout or script-injection findings, and seven use read-only permissions. However, 28 of 41 action references are unpinned and high-confidence audits found ad hoc package installs; these are avoidable workflow supply-chain hygiene gaps, while trusted publishing was only informational.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
oxc-parser Version ^0.148.0 | — | — |
eslint-scope Version ^9.1.2 | — | — |
lightningcss Version ^1.33.0 | — | — |
eslint-visitor-keys Version ^5.0.1 | — | — |
@shaderfrog/glsl-parser Version ^7.0.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.