awesome/crc_fast

Workflow auditdanger

Both workflows were analyzed, but the Windows release workflow uses a workflow_run trigger alongside five high-confidence template-injection findings and top-level write permissions; five of eight action references are unpinned. This creates a material release-pipeline supply-chain concern.

Release historycaution

There are only two releases across roughly 17 months, with a median interval of about 214 days and one release in the last 12 months. This is a thin release history and leaves limited evidence of sustained maintenance.

Repo commit activitycaution

The repository had zero commits and zero active maintainers in the last three months. Combined with the sparse release history, this is meaningful evidence of currently quiet maintenance.

Repo popularitycaution

The repository has six stars and three forks. This is limited adoption evidence, but popularity is supporting context rather than a decisive health measure.

Repo toolingcaution

The repository uses Composer for builds, but no security-scanning tool was detected. The missing scanner is a hygiene gap, partly offset by the visible tests and workflow coverage.