pacificnm/pacificnm-log

Release historydanger

The package has had no releases in over nine years: its latest release was on January 1, 2017, despite only three releases overall. This 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 long release gap and leaving current maintenance un demonstrated.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. That leaves a modest maintenance and vulnerability-management gap.

Security policycaution

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a hygiene gap rather than evidence that the package is unsafe on its own.