apiki/wpsteak

Release historycaution

The package has had no release in about six years, despite four releases over its earlier 15-month period. That strongly limits confidence in ongoing maintenance, although the repository remains available and unarchived.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. The repository's recent push metadata does not compensate for the absence of observed commit activity.

Repo toolingcaution

Composer and Make tooling are present, but no security scanning tools were detected. This is a transparency and maintenance-hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a modest transparency gap, partly offset by the organization-backed repository and existing development tooling.

Workflow auditcaution

Both workflows were analyzed without high- or medium-severity findings and have no untrusted checkouts or script injection, but all five action references are unpinned. The missing top-level permissions blocks are acceptable on their own.