beastbytes/yii-leaflet

Release historycaution

There has been only one release, about 1 year 8 months ago, with none in the last 12 months. This is a meaningful maintenance concern for a dependency, although the source repository was pushed more recently.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. That weakens evidence of active maintenance despite the more recent push timestamp.

Repo toolingcaution

The project uses Composer build tooling, but no security scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but does not by itself make the release unfit.

Workflow auditcaution

The sole workflow gives top-level write permissions and all five analyzed action references are unpinned. The audit found no untrusted checkout, injection, or high-confidence dangerous findings, so this is a hygiene caution rather than a severe risk.