joris/laravel-skeleton

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, after roughly 16 months since the last push. This materially raises abandonment risk for a framework-dependent starter project.

Project backingcaution

The repository is owned by an individual rather than an organization, so the project has no demonstrated organizational backing. This makes the absence of recent activity more consequential.

Release historycaution

Only two releases were published, both about 16 months ago, with no releases in the last 12 months. This is meaningful evidence of a dormant release line for a framework skeleton.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap, not evidence that the release is unsafe on its own.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers transparency for a project intended to seed web applications.