crcms/file-config

Release historydanger

The latest release was in April 2018, and there have been no releases in the last 12 months. This long period without updates is a substantial abandonment risk, despite the package having seven releases overall.

Repo popularitycaution

The repository has only 2 stars, 1 fork, and 0 watchers. Popularity is not required for a healthy package, but these figures provide little supporting evidence of broad review or ongoing community use.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.

Repository archivedcaution

The repository is not archived, which leaves the project technically maintainable, but its last push was also in April 2018 and does not offset the stale release history.

Security policycaution

No security policy was found in the repository. This is a transparency gap, although it is less significant for this small package than the prolonged lack of releases.