carbon/primarycontent

Release historydanger

The package has 19 releases since 2018, but its latest release was about four years ago and it had no releases in the last 12 months. That long gap materially increases abandonment and compatibility risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the package's roughly four-year release gap. This indicates limited current maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a minor transparency gap for a package with otherwise clear project documentation.