zver/finder

Risky to adopt for new projects: this package has had no release or repository activity since June 2016. It has tests, documentation, a license, and no runtime dependencies, but its decade-long inactivity leaves maintenance and compatibility concerns.

Latest 1.0.0

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

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 of abandonment risk despite the package not being deprecated.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the last push being about 10 years ago. This materially increases the risk that defects or compatibility problems will go unaddressed.

Project backing

The repository is owned by an individual user rather than an organization, so there is no observed organizational backing to compensate for the thin maintenance evidence.

Repo popularity

The repository has zero stars and forks and only one watcher, offering little community evidence or backup support. Popularity is supporting evidence rather than decisive on its own, but it provides no compensation for the stale release history.

Repo tooling

Composer is used as a build tool, which supports reproducible project handling, but no security scanning tools are present. The missing scanning is a modest transparency gap rather than a standalone reason to reject the package.