This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.
5%
Total Score
75
50
50
The complete artifact contains only README.md and package.json, confirming that this release is a name-holding artifact with no implementation files.
The package has a README, but it explicitly says the name is being held by npm and offers no usable implementation. That makes the package unsuitable as a dependency rather than merely poorly documented.
The package has only four releases, with none in the last 12 months; its latest release was in August 2016. This indicates a long-dormant package, consistent with a reserved name rather than an actively maintained dependency.
The linked repository recorded zero commits and zero active maintainers in the last three months. Although the repository is organization-owned, there is no observed recent maintenance to offset the package's inactivity.
The repository name does not match the package name and its README does not mention fs. In this case the mismatch aligns with the README's security-holding purpose, but it provides no evidence that fs is a functional project.
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.