prolib/stricter

Its small dependency surface, organization backing, and lack of install-time scripts reduce operational concerns. The package is otherwise too minimal for confident long-term adoption.

Latest v1.0

Packagist

38%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published in August 2017, with no releases in the last 12 months. This long period without a new release is strong evidence of abandonment risk.

License

Neither the package nor the linked repository provides a recognized license declaration or license file. That creates a material legal and transparency gap for dependency adoption.

Package file tree

The artifact and repository each contain only three files: composer.json, src/Stricter.php, and .gitignore. This is unusually minimal and provides little project documentation or maintenance context.

Package scaffolding

The package has no README, tests, or changelog, although tests and changelogs are normally repository concerns and are not expected in every published artifact. The missing README still weakens consumer-facing transparency for a library.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful external evidence of active use or review.