zrnik/file-dump

The README, MIT declaration, matching repository, and simple dependency profile make the package easy to inspect. Its one-person ownership and absent security tooling reduce resilience if maintenance is needed.

Latest v0.0.1

Packagist

44%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over four years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo commit activity

The repository recorded no commits and had no active maintainers in the last three months, consistent with the package's long period without releases. This materially increases maintenance and abandonment risk.

Project backing

The repository is owned by an individual user rather than an organization. Combined with the single registry maintainer and absent recent activity, this indicates limited visible backing and resilience.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counts provide little supporting evidence of community review or shared maintenance.

Repo tooling

Composer is used for builds, but no security scanning tooling is present. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.