tarsana/filesystem

MIT licensing, included tests, and no runtime dependencies make adoption straightforward. Repository maintenance and security-process coverage are limited, so future support is uncertain.

Latest 2.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was published over eight years ago. This is strong evidence of stale registry publication, even though the source repository is not archived.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, leaving current maintenance capacity unverified and increasing abandonment risk.

Repo issue activity

There are no open issues or pull requests and no recent issue activity. This is consistent with a small, quiet project but provides little evidence of active support.

Repo popularity

The repository has 4 stars, 1 fork, and 3 watchers. This indicates a small user base, but popularity is only supporting evidence and does not independently determine health.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. The missing automated security coverage is a modest transparency and maintenance concern.