ajiho/namespaceify

The package is small but clearly linked to its source repository, has an MIT license, a usable README, and no install-time scripts. Its minimal tooling and absent security policy add little assurance for a dependency that has seen no maintenance for over two years.

Latest v1.0.1

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in May 2024, with none in the last 12 months. This provides limited evidence of ongoing maintenance for a package now about two years old.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance 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 reduces transparency for a package used in application dependencies.

Workflow audit

No GitHub Actions workflows were present, so there is no detected workflow attack surface or workflow hygiene issue. This also provides no evidence of automated maintenance or security checks.