osit/webaseo

The README and release metadata give consumers a clear starting point, and the package is licensed with no install-time scripts. Its small maintenance footprint and absent security policy make long-term fixes and security reporting less dependable.

Latest v1.0.2

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only three releases, all around its first publication on December 11, 2023, and none in the last 12 months. This strongly indicates stalled maintenance for a package now over two years old.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the evidence of prolonged inactivity rather than a merely slow release cadence.

Maintainers

Only one account has registry publishing access, leaving little visible publishing redundancy. The linked repository is user-owned rather than organization-owned, so there is no provided backing signal to offset this thin base.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That weakens assurance for future maintenance, especially alongside the inactive repository.

Security policy

The repository has no security policy, leaving users without a documented channel or process for reporting vulnerabilities. This is a transparency and maintenance gap, though it is not evidence of malicious behavior.