ctw/ctw-middleware-apex

Project backingcaution

The repository is owned by an individual rather than an organization, so the single-maintainer concentration is not buffered by visible organizational backing. Recent commits and releases still show that the project is actively maintained.

Repo bus factorcaution

One contributor made all 29 commits in the last 3 months, giving the project a complete single-maintainer concentration. The active repository offsets abandonment concerns but does not remove succession risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a modest repository-hygiene gap, not a severe risk on its own.

Security policycaution

The repository has no security policy. For a small middleware package this is a transparency gap, though active maintenance and clear project structure provide some compensation.

Workflow auditcaution

The workflow was fully analyzed, uses read-only permissions, and has no untrusted-trigger sinks or audit findings. Its one action reference is unpinned, which is a supply-chain hygiene weakness but not a severe risk alone.