Package Health/getpop/markdown-convertor

getpop/markdown-convertor

This is a healthy, actively maintained release with a three-year history, 131 releases, 33 releases in the last 12 months, and a stable non-prerelease version. The package is licensed, tested, small in scope, transparently linked to a matching organization-owned repository, and has recent repository activity. The main adoption risks are that all 14 recent commits came from one contributor, the repository has minimal popularity, and no security policy or security-scanning tooling was observed; these are meaningful governance and resilience gaps but are outweighed by the strong release cadence, non-archived repository, complete package tree, and organization backing.

Latest 19.2.4

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made 100% of the 14 commits in the last 3 months, creating a genuine continuity risk; organization ownership provides some mitigation but does not demonstrate a second active contributor.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and open issue count is unknown. This provides little evidence of community support, though it does not show unresolved backlog.

Repo popularity

The repository has only 1 star and 0 forks, indicating limited community validation; this is supporting caution rather than a decisive health problem because release and commit activity are strong.

Repo tooling

Composer build tooling is present, but no security-scanning tools were observed. The missing security automation is a governance gap, while the package's tests and static-analysis configuration provide partial engineering compensation.

Security policy

The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting and response expectations less explicit.