kcs/filesystem
Tests and a matching README provide useful project evidence, while the MIT declaration and build tooling are clear. All nine workflow actions are unpinned and no security policy is published, adding hygiene concerns.
58%
Total Score
50
100
83
83
Health Score Breakdown
Only one account has registry publish access. With the repository owned by an individual rather than an organization, this leaves a relatively thin publishing and support base.
The registry namespace and repository are tied to an individual owner rather than an organization, providing less visible institutional backing for long-term maintenance.
Only two releases exist, with the latest published about 2 years and 5 months ago and none in the last 12 months. This is a meaningful maintenance concern for a library dependency.
There were no commits from active maintainers in the last 3 months. Combined with the stale registry release history, this raises abandonment risk.
The repository has 1 star, 0 forks, and 1 watcher. This is weak supporting evidence for maturity, though popularity alone does not determine whether a small package is healthy.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Alessandro Chitolina |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 kcs/stream Version ^0.1.1 | — | — |
symfony/mime Version >=5.4 | — | — |
doctrine/collections Version ^1.0 || ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 2 years 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.