File System Access API implementation backed by core filesystem primitives
82%
Total Score
healthy
Healthy: frequent releases and active repository maintenance outweigh the concentrated contributor base.
The repository is owned by a user rather than an organization, so the concentrated contributor activity is not visibly buffered by organizational backing. Other repository activity still shows active maintenance.
Three contributors were active, but the top contributor made about 90% of recent commits. That concentration is a meaningful continuity concern, even though other contributors remain active.
TypeScript and npm build tooling are present, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence of abandonment.
All three workflows were analyzed with no untrusted checkout or script-injection findings. However, all five action references are unpinned, one workflow has top-level write permissions, and a high-confidence low-severity finding reports installing a package outside a lockfile.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
thingies Version ^2.5.0 | — | — |
@jsonjoy.com/fs-core Version 4.80.0 | — | — |
@jsonjoy.com/fs-node-utils Version 4.80.0 | — | — |
@jsonjoy.com/fs-node-builtins Version 4.80.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.