ultimate-multisite/ai-provider-for-any-openai-compatible

Repo bus factorcaution

Two contributors were active, but the top contributor made 10 of 11 commits, or about 91%. The second active contributor partly compensates for this concentration, but the project still has a meaningful continuity risk.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. Although name differences can occur with subpackages, the absence of both a name match and README reference raises concern that the repository linkage may not clearly identify the published package.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces repository security transparency, while build tooling and lockfiles provide some compensating hygiene.

Security policycaution

The repository has no security policy. This leaves vulnerability reporting and disclosure expectations unclear, creating a transparency gap for dependents.

Token permissionscaution

All 3 workflows lack top-level permissions declarations, and none declares read-only permissions. No workflow has top-level write permissions, which limits the observed risk, but explicit least-privilege configuration is still missing.