rozbehsharahi/meedia

Its single registry maintainer, absent security policy, and lack of security scanning limit ongoing support visibility. The README, tests, MIT license, and release notes provide useful transparency, but do not offset the package's long-term inactivity.

Latest 0.1.2

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published on December 21, 2017, and there were no releases in the last 12 months. Five releases arrived early in the package's life, but the nearly nine-year release gap indicates likely abandonment.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No newer activity is provided to compensate for this inactivity.

Maintainers

Only one registry maintainer is listed, which leaves little visible publishing capacity for a user-owned project. This is a smaller concern than the observed inactivity but still increases continuity risk.

Repo tooling

Composer is used as the build tool, which supports reproducible package management, but no security scanning tools are present. This is a hygiene gap rather than evidence of unsafe code by itself.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. The package remains licensed and has repository source, but that does not provide an incident-response path.