mb4it/filesystem
Six releases in about seven months, a clear MIT license, and a substantial test suite support a usable foundation. The repository has no security policy, so security-reporting expectations are unclear.
67%
Total Score
67
94
75
Health Score Breakdown
The repository owner is an individual user rather than an organization, so there is no shown organizational handoff capacity to offset the concentrated contributor base.
One contributor made all two commits in the last three months, giving the project a concentrated maintenance base. With no organization backing shown, this increases continuity risk.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, and the package's young age limits how strongly these counts should affect the score.
The repository has no SECURITY policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency and maintenance-process gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Maxim Bezvodinskikh |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mb4it/collections Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 7 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.