frdl/cms

Release historydanger

The package has had only two releases, with the latest published over four years ago and none in the last 12 months. That long release gap is a substantial maintenance concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this indicates weak current maintenance.

Repo toolingcaution

Composer is used for builds, which is appropriate for this package, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled. This is a secondary concern alongside the maintenance signals.

Version stabilitycaution

Version v0.0.2 is not a stable major release, so the API and behavior may still change. This compounds the risk of relying on an old, inactive release.