lionar/file-system

The MIT declaration, tests, and release notes provide useful transparency, while the small runtime dependency set limits exposure. Its README explicitly says the API is experimental, so compatibility may change if development resumes.

Latest v0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence that the package is no longer maintained.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the one-release history, this indicates sustained abandonment rather than a temporary pause.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no evidence of an active user community.

Repository archived

The repository is not archived, which avoids the strongest abandonment signal, but its last push was about 10 years ago. The non-archived status does not compensate for the prolonged inactivity.

Security policy

The linked repository has no security policy. This is a transparency gap, although it is secondary to the much stronger evidence of long-term inactivity.