shipmonk/name-collision-detector

Release historycaution

The package has five releases since December 2022, but none in the last 12 months and the latest registry release was over two years ago. The recent repository activity partly offsets, but does not remove, this release-cadence concern.

Repo bus factorcaution

All one recent commit came from a single contributor, creating concentrated maintenance risk. Organization ownership provides some backing, but no second active contributor is shown.

Repo commit activitycaution

There was one commit in the last three months, showing some current activity, although the very low volume does not fully offset the stale registry release history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving security hygiene less transparent.

Security policycaution

The repository has no security policy, so users are given no documented vulnerability-reporting process.