fwhy/blast

Release historydanger

The latest release was in June 2022, and there have been no releases in the last four years. That long release gap is strong evidence of abandonment risk for a package still below 1.0.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no recent maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, especially alongside the lack of recent activity.

Security policycaution

The repository has no security policy, so users have no documented process for reporting vulnerabilities or understanding security response expectations.