samsonasik/naming

Recent releases and a matching repository with a clear README provide useful continuity. The project has one registry maintainer, no security policy, and all three workflow actions are unpinned, so oversight and build reproducibility are limited.

Latest 4.1.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. The matching repository and recent releases provide some compensation, but a single publisher leaves limited visible succession capacity.

Project backing

The package and repository are owned by the same individual account, so the source location is coherent, but there is no organization backing to broaden maintenance capacity.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months. Recent releases partly offset this, but the current development activity is thin.

Repo popularity

The repository has 7 stars, 0 forks, and 1 watcher. This indicates a small user and contributor footprint, though popularity is supporting evidence rather than a health verdict.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The absence of scanning is a modest transparency and maintenance gap, not a severe risk by itself.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Abdul Malik Ikhsan

Direct Dependencies

Dependency	Last Release	Score
webmozart/assert Version ^1.11 \|\| ^2.1	—	—
laminas/laminas-filter Version ^3.2	—	—
samsonasik/array-lookup Version ^1.8 \|\| ^2.2	—	—
laminas/laminas-validator Version ^3.8	—	—
symfony/polyfill-mbstring Version ^1.33	—	—