florianwolters/component-core-immutable

Release historydanger

The latest release was in May 2014, with no releases in the last 12 months and only two releases overall. That long gap is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the package having received no repository activity since 2014. This materially increases abandonment risk.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. While a clean tracker is not inherently bad, alongside the absent commits it provides no evidence of active support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a secondary hygiene gap rather than the main reason the release is risky.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds transparency risk, especially for a dependency with no recent maintenance.