jimbojsb/adore

Its tiny four-file layout and clear Composer dependencies make the code easy to inspect. The README warns that the API may change, while the lack of tests and security tooling leaves little protection for future adoption.

Latest v0.1

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published over 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, although the repository is not archived or deprecated.

Repo commit activity

The repository has recorded no commits and no active maintainers in the last three months, consistent with the last push occurring in 2016. This materially increases abandonment risk.

Package file tree

The artifact and repository contain only four files, including a README, Composer manifest, and one source file. This is easy to inspect but also provides little evidence of mature project infrastructure.

Repo tooling

Composer is used for builds, but no security scanning tooling is present. That is a modest transparency and maintenance gap for a dependency intended for application use.

Security policy

The repository has no security policy. For an old, inactive package this leaves no documented process for reporting or handling vulnerabilities.