bricks81/bricks-config

Risky to adopt: the latest release was published nearly nine years ago and the repository has had no commits in the last three months. It is not deprecated or archived and has a clear MIT license, but the very small project footprint and repository/package mismatch make ongoing support uncertain.

Latest 0.1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has four releases, but none in the last nine years; the latest release was published on March 10, 2017. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the last push in 2020, this materially increases abandonment risk.

Package scaffolding

The published artifact lacks a README, tests, and changelog, but those omissions are normal for many compiled or minimal packages; the repository file tree does include a README. The absence of repository tests and changelog is a modest transparency concern for a library.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. A clean issue tracker can be positive, but here it offers no evidence of active maintenance.

Repo package mention

The repository name does not match the package name and its README does not mention the package. This raises uncertainty about whether the linked repository is the package's actual source, despite the matching owner namespace.