pacificnm/pacificnm-page

Release historydanger

The package has only three releases, all concentrated between December 29, 2016 and January 1, 2017, with no release in over nine years. This is strong evidence of abandonment despite the stable version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with no meaningful activity since January 2017. This is the main abandonment risk for a dependency.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little supporting evidence of active adoption or community maintenance. Popularity is supporting evidence, so this reinforces but does not independently determine the verdict.

Repo toolingcaution

The repository uses Composer, which fits the package ecosystem, but no security-scanning tools were detected. That is a maintenance and transparency gap, though it is less serious than the prolonged inactivity.

Security policycaution

No security policy was found in the repository, leaving vulnerability reporting and response expectations unclear. This matters more because the project also shows no recent maintenance.