xiaobingge/filesystem

The repository has no stars, security scanning, or security policy, leaving little evidence of ongoing review. Its MIT licensing and small dependency set reduce adoption friction, but the project offers limited validation for a library dependency.

Latest 1.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Package scaffolding

The package has no README, tests, or changelog, while the exact version does have a GitHub release. The missing README and tests limit consumer guidance and validation for this library.

Project backing

The repository is owned by an individual user rather than an organization. Combined with the single release and stale repository activity, this indicates limited visible project backing.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful community signal.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of unsafe code.