divineomega/do-file-cache

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no distinct replacement identified because the listed replacement is the same package. This is a severe adoption and continuity risk despite other recent activity.

Repo bus factorcaution

All recent commits came from one contributor, giving the project a single-person maintenance dependency. The repository is user-owned, so no organizational handoff evidence compensates for that concentration.

Repo commit activitycaution

The repository had 2 commits in the last 3 months, showing some recent activity, but the volume is limited and does not by itself demonstrate strong maintenance capacity.

Security policycaution

The repository has no security policy. This is a transparency gap for reporting and handling vulnerabilities, although it is less severe than the package-level abandonment status.

Workflow auditcaution

The sole workflow was fully analyzed with no dangerous triggers or audit findings, but both action references are unpinned. Missing top-level permissions is acceptable here and is not a concern on its own.