Node.js standard library dependencies for fs-related packages
76%
Total Score
healthy
Healthy, supported by frequent releases and active repository work, with concentrated ownership and repository-link concerns.
One contributor made about 90% of the recent commits, and the repository owner is an individual rather than an organization, leaving a meaningful continuity risk despite two additional contributors.
The linked repository name does not match the package name and its README does not mention this package, so the package-to-repository relationship is not clearly demonstrated even though it may be a monorepo subpackage.
The project uses TypeScript and npm build tooling, but no security-scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of abandonment.
All three workflows were analyzed with no untrusted checkout or script-injection paths, but all five action references are unpinned, one workflow grants top-level write access, and a high-confidence low-severity finding installs a package outside a lockfile.
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.