bregananta/blockchain

Release historydanger

Only two releases were published, both in 2017, with no release in roughly 8 years and 11 months. That long release silence is strong evidence of abandonment for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push occurring in 2017. This leaves current maintenance capacity un demonstrated.

Maintainerscaution

One registry maintainer is listed. A single maintainer is not inherently unhealthy, but here it provides little resilience alongside the long-standing absence of releases and commits.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than a severe risk, especially given the package's very small file tree.

Security policycaution

The repository has no security policy, so consumers have no documented route for reporting vulnerabilities or understanding security handling. The package's tests and license do not compensate for this transparency gap.