ginsen/uri

Tests, documentation, licensing, and a clean repository identity provide a solid foundation. Maintenance has stopped after an initial burst, with no recent commits and no security policy, so future fixes are uncertain.

Latest v1.0.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The linked repository is also owned by that same individual, so there is no organization-backed maintainer base to offset single-person continuity risk.

Release history

The package has three releases, all clustered within about two days, followed by more than a year without a release. That suggests a small or dormant project, though the existing stable release remains available.

Repo commit activity

There have been no commits and no active maintainers in the last three months, consistent with a project that has been dormant for over a year. This materially increases the risk that defects will not receive fixes.

Repo popularity

The repository has zero stars, forks, and watchers, indicating little visible adoption. Popularity is only supporting evidence, so this adds modest uncertainty rather than determining the verdict.

Repo tooling

The repository uses Make and Composer, showing basic build support, but no security-scanning tooling is present. That is a modest transparency and maintenance gap rather than a severe risk.