hibrido/register

The repository has no security scanning or security policy, and its published contents contain only three metadata files. The MIT license and organization ownership provide limited transparency, but do not offset the lack of activity.

Latest 0.0.1

Packagist

32%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published nearly five years ago, with no releases in the last 12 months. That strongly suggests the package is abandoned or was never developed beyond registration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the old release date and providing no evidence of ongoing maintenance.

Package file tree

The artifact and repository each contain only .gitignore, LICENSE.txt, and composer.json. That may fit the stated namespace-registration purpose, but it leaves no implementation or consumer documentation to assess.

Repo tooling

Composer is used as the build tool, but no security-scanning tools are present. This is a modest supply-chain hygiene gap rather than evidence of an unsafe release by itself.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is secondary to the lack of maintenance.