imedge/web-url-signing

Usable with caveats: the package is licensed, small in scope, backed by an organization, and includes tests and automated checks. However, it has had only one release in nearly two years, no commits in the last three months, and provides almost no README guidance.

Latest v0.1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

Tests are present in the artifact and repository, but the README is only 14 characters and gives consumers essentially no integration guidance. The missing changelog is normal for a published artifact and is not treated as a gap.

Release history

This is the only release, published about 1 year 11 months ago, with no releases in the last 12 months. That leaves maintenance and compatibility maturity largely unproven.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the single historical release, this is meaningful evidence of limited recent maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. For a small library this is a hygiene gap rather than a standalone severe risk.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.