andyfraussen/laravel-dokapi-client

Project backingcaution

The repository is owned by an individual account, consistent with the single-person publishing context; recent activity and a second contributor provide some, but not organizational, maintenance backing.

Release historycaution

Only three releases have been published over 241 days, with a median interval of about 97 days. Recent repository activity partly offsets the limited release history, but there is still modest evidence of long-term release maturity.

Repo bus factorcaution

One contributor made 11 of 12 recent commits, so maintenance depends heavily on a single person. A second active contributor provides limited compensation, but the concentration remains a real continuity concern for this individually owned project.

Security policycaution

No repository security policy was found, leaving vulnerability reporting expectations unclear. This is a transparency gap, but it is not evidence that the package is unsafe by itself.

Workflow auditcaution

The sole workflow was fully analyzed with no injection, untrusted-checkout, or high-severity findings. However, both referenced actions are unpinned, which weakens build reproducibility and supply-chain hygiene.