Package Health

pop-schema/menus

This is a healthy, actively maintained release with a strong five-year history, 162 releases, 33 releases in the last 12 months, and a recent repository push. It has stable versioning, a non-deprecated registry entry, an explicit GPL license with a license file, tests in the artifact and repository, a matching repository with an organization owner, and no install-time lifecycle scripts. The main concerns are that all recent repository commits come from one contributor, no security policy or security-scanning tooling is present, and the package/repository lacks a changelog despite documenting one; these reduce resilience and transparency but do not outweigh the evidence of ongoing maintenance. Confidence is high but not maximal because several security, dependency, provenance, and activity signals were not collected.

Latest 19.2.4PackagistPackagist

82%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

80

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

90

Health Score Breakdown

Repo bus factorcaution

All 15 commits in the last three months came from one contributor, creating a genuine continuity risk; organization ownership provides some potential handoff capacity but no second active contributor is evidenced.

Repo issue activitycaution

There were no new issues or pull requests in the last month and no merged pull requests, which provides little evidence of community activity; however, this is partly offset by 15 recent commits and the absence of open pull requests.

Repo popularitycaution

The repository has only 1 star and no forks, indicating limited public adoption; this is supporting evidence only and is outweighed by the package's strong release and commit activity.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools are present, leaving a security-hygiene gap that lowers transparency without indicating abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Leonardo Losoviz

Direct Dependencies

DependencyLast ReleaseScore
getpop/engine
Version ^19.2.4
—
—
pop-cms-schema/taxonomies
Version ^19.2.4
—
—

Weekly Downloads

Info

Last Published
19 days ago
Created
5 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform