laravelwebdev/responsive

Release historydanger

Only two releases were published, with the latest about five years ago and none in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers during the last three months. Combined with the old release history, this indicates little current maintenance capacity.

Project backingcaution

The package and repository are owned by the same individual account, so the source ownership is consistent. Individual ownership does not provide the maintenance capacity of an organization-backed project.

Repo issue activitycaution

Two issues and one pull request remain open, with no new or closed activity in the last month. This is supporting evidence that reported work is not being handled actively.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tooling is present. For a small theme this is a modest transparency and maintenance gap, not a standalone severe risk.