programster/core-libs

The project has a long release history, recent publishing, tests, and a clear license. The linked repository does not identify or mention this package, while one-person maintenance, no recent commits, and no security policy leave meaningful transparency and continuity concerns.

Latest 2.6.5

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access, and the project is owned by an individual rather than an organization. The active release history partly offsets the limited apparent maintainer redundancy.

Repo commit activity

There were no commits and no active maintainers during the last 3 months. The repository was pushed on the release date and the registry shows regular releases, which softens but does not remove the concern about ongoing source maintenance.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That raises a concrete concern that the linked source may not actually correspond to this release.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and maintenance gap rather than evidence of a defect.

Security policy

The repository has no security policy. That leaves vulnerability-reporting and response expectations undocumented for a package that provides filesystem, network, and encryption helpers.