doowebdev/doo-csrf

Release historydanger

Only one release exists, published about 12 years ago, with no releases in the last 12 months. That leaves the package without evidence of ongoing maintenance or adaptation.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating substantial abandonment risk.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This reduces evidence of ongoing dependency and code-health monitoring.

Security policycaution

The repository has no security policy, which is a meaningful transparency gap for a package specifically intended to help prevent CSRF.