code-and-commits/patch-apply

Release historydanger

The package has had only one release, with no releases in more than five years. That strongly limits evidence of ongoing maintenance, though the package is not marked deprecated.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, while its last push was in October 2020. This is strong abandonment evidence for a library dependency.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little external evidence of maturity or community support.

Repo toolingcaution

Composer build tooling is present, which supports a conventional project setup, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy. For a small package this is a transparency gap, although the absence does not by itself show unsafe code or abandonment.