dmk/mkvarnish

Repo commit activitycaution

No commits and no active maintainers were recorded in the last three months, which is a maintenance concern. The very recent release and repository push partly offset this, but do not demonstrate sustained development activity.

Repo popularitycaution

The repository has three stars and two forks, so external adoption appears limited. Popularity is supporting evidence rather than a decisive health measure, and the package has stronger maintenance and backing signals.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and preventive-maintenance gap rather than evidence of unsafe code.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting and response expectations unclear.

Token permissionscaution

Both analyzed workflows lack top-level token permissions declarations. Although neither grants top-level write access, explicit least-privilege settings would provide better workflow hygiene.