madalintomescu/laravel-blog

Release historydanger

The package has only two releases, with the latest published nearly eight years ago and none in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

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

Lifecycle scriptscaution

The package defines post-autoload-dump, post-create-project-cmd, and post-root-package-install scripts. These may be normal Laravel setup hooks, but install-time execution increases dependency-install complexity and deserves review.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The project's README and tests provide some compensating transparency, but not a response process.