bricks-framework/application

Release historydanger

The package has only one release, published nearly six years ago, and none in the last 12 months. This is strong evidence of an unmaintained dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating current maintenance has stopped.

Project backingcaution

The repository is owned by a user account rather than an organization, so there is no provided evidence of broader project backing to compensate for the single-maintainer and inactivity concerns.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap, not evidence of malicious behavior.

Repository archivedcaution

The repository is not archived, which is a compensating signal, but it was last pushed nearly six years ago and therefore does not offset the inactivity evidence.