mikrofraim/framework-core

Release historydanger

The latest release was about 4 years and 6 months ago, with no releases in the last 12 months. Five total releases show some history, but the long gap is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with maintenance having stopped for about 4 years and 6 months. This is the strongest evidence that adopting the package may create abandonment risk.

Dependency profilecaution

The package declares 24 runtime dependencies, spanning framework, HTTP, caching, routing, logging, and templating components. That broad dependency surface increases maintenance and compatibility risk for a package with no recent releases.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a transparency and maintenance weakness, though it is less serious than the prolonged inactivity.

Security policycaution

The repository has no security policy. That leaves vulnerability reporting and response expectations unclear, adding a transparency gap for a framework package.