empaphy/polyphill-intl

Its narrow metapackage role and single runtime dependency make it easy to assess and adopt. Maintenance evidence is limited: only one release arrived in the last year and there were no commits in the last three months. Licensing and package identity are clear, but no security policy is published.

Latest 1.0.2

Packagist

73%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has three releases over about 23 months, with one release in the last 12 months and a median interval of about 303 days. This shows some maintenance but a sparse cadence.

Repo commit activity

There were no commits and no active maintainers in the last three months. The recent release provides some compensating evidence, but ongoing maintenance capacity is still limited.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. For a tiny metapackage this is a modest transparency gap rather than a severe risk.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's small scope limits the practical impact.