jardissupport/workflow

Repo bus factorcaution

One contributor made all five commits in the last three months, creating a meaningful continuity risk. Organization backing provides some handoff capacity but does not replace a second active contributor.

Repo commit activitycaution

Five commits in three months show ongoing work, but the activity is modest and concentrated in one active maintainer.

Security policycaution

The repository has no published security policy, leaving vulnerability reporting and response expectations unclear.

Workflow auditcaution

All seven action references are unpinned, and the audit found a high-confidence template-injection issue in the release workflow. There is no untrusted checkout or pull-request-target trigger, so this is a hygiene and workflow-risk concern rather than a standalone severe verdict.