interfrog/if_sporty

The package has a focused file tree, a declared GPL license, and only one runtime dependency. Documentation is minimal, while repository security practices and community activity provide little evidence of ongoing support.

Latest 1.1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both in May 2018, with no releases in the last 12 months and a package age of over eight years. This is strong evidence of abandonment risk for a dependency.

Package scaffolding

The artifact includes a changelog and a README, and the absence of tests is normal packaging practice. The README is only 21 characters long, so consumer documentation is notably thin.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a very quiet project and offers no evidence of active maintenance.

Repo popularity

The repository has zero stars and forks and only three watchers. Popularity is supporting evidence rather than a verdict, but these numbers provide little outside evidence of active adoption.

Repo tooling

Composer is used for builds, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than a severe risk by itself.