linclark/microdata-php

MIT licensing, tests, a README, and no runtime dependencies make the package easy to inspect and integrate. Its unresolved repository work and weak project security documentation add uncertainty on top of the long maintenance gap.

Latest 2.0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest of only three releases was published 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being deprecated.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months, consistent with the six-year gap since the last push and materially increasing abandonment risk.

Repo issue activity

There was no issue or pull-request activity in the last month, while two issues and six pull requests remain open. This suggests limited current maintainer response.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so the repository-to-package relationship is less transparent than expected.

Repo tooling

Composer is used for builds, but no security-scanning tool is present. For a small, old library this is a modest transparency and maintenance weakness.