mdxdave/time-ago

Clear documentation, an MIT license, and a matching source repository make the package straightforward to inspect. Its small project footprint and lack of security tooling leave limited operational evidence beyond the current code.

Latest 1.2.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, so the ownership path is consistent. This also means the project has a single-person backing model rather than organizational support.

Release history

The package has four releases across more than nine years, with no release in the last 12 months and a median interval of about 910 days. This indicates a slow maintenance cadence, though it may fit a small, stable plugin.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the lack of recent registry releases, this is evidence of currently inactive maintenance.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. For a small plugin this is a modest hygiene gap, not evidence of abandonment by itself.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a limited concern for a small package with no other observed repository risk.