hazzard/config

Release historydanger

This package has had only one release, on April 16, 2015, with no releases in the last 12 months. That long period without published updates is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged lack of releases. No provided activity signal compensates for this inactivity.

Package scaffoldingcaution

A README is present and the release has a GitHub release record; the absence of tests and a changelog in the published package is normal packaging practice. The README is extremely short, limiting consumer guidance.

Repo toolingcaution

Composer is used as the build tool, but the repository has no security-scanning tooling. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This adds a transparency gap alongside the long inactivity.