jvmtech/neos-hardening

Usable with caveats. The package is actively published by an organization and has a current stable release, but its low release cadence, no commits in the last three months, and lack of security tooling or policy reduce confidence in ongoing maintenance.

Latest 2.0.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 4 years and released twice in the last 12 months, but its median interval is about 186 days, indicating a relatively slow maintenance cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which is a meaningful concern for a security-focused package despite the recent release and push.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing transparency for a package whose purpose concerns backend security.

Security policy

The repository has no security policy, leaving users without a documented channel or process for reporting vulnerabilities in a security-focused package.