danielcembranelli/cnab_yaml

Release historydanger

The latest release was in June 2018, and there have been no releases in more than eight years despite the package being over eight years old. This is strong evidence of abandonment risk, though the repository is not marked archived.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This materially lowers confidence that defects or changing bank formats will be addressed.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Low popularity is supporting evidence rather than a verdict, but it provides no community signal to offset the lack of recent maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a hygiene weakness that adds limited concern alongside the much older maintenance record.

Security policycaution

The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a modest transparency gap, not a standalone reason to reject the package.