blast/config

Release historydanger

Only three releases were published, and none appeared in the last 12 months; the latest release was about 10 years ago. This is strong evidence of abandonment, though the stable 1.0.2 release provides some maturity.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since the last release. No provided signal shows current maintenance capacity.

Repo issue activitycaution

There were five open issues but no new or closed issues, pull requests, or merged pull requests in the last month. This adds evidence that reported problems are not being actively managed.

Security policycaution

The linked repository has no security policy. For a configuration library this is a transparency and vulnerability-reporting gap, although the package is small and the artifact is otherwise documented.