lambry/bloc

Release historydanger

Only one release exists, published nearly four years ago, with no releases in the last 12 months. This is strong evidence of an inactive package, although it is not marked deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the single-release history, this indicates a substantial abandonment risk.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools are configured. That is a modest transparency and maintenance gap for a package containing executable PHP and JavaScript.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but its last push was in October 2022 and does not offset the broader inactivity evidence.

Security policycaution

No security policy is present in the linked repository. This weakens the project's response and disclosure transparency, though it is not by itself evidence of unsafe code.