joaoppcastro/filamentcms

Release historydanger

Only two releases were published, both in January 2024, with no releases in the following 2 years and 8 months. This is strong evidence of abandonment for a package intended as an active CMS dependency.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and indicating no observed maintenance capacity.

Licensecaution

The manifest declares MIT, but the artifact license file is detected as GPL-3.0. Although a license file is present, the mismatch creates a material legal and adoption concern that must be resolved.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem. No security scanning is configured, leaving a modest repository hygiene gap, but this does not outweigh the maintenance evidence.

Security policycaution

The repository has no security policy, reducing transparency about vulnerability reporting and response. This is a secondary concern because the dominant risk is the prolonged lack of maintenance.