rimba/dms

Usable with caveats: the package is actively released and backed by an organization, but it has only one active contributor and lacks tests, a README, and a changelog. Review the release workflow and package behavior before adopting it in a critical system.

Latest v1.4.7

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository contain no tests, README, or changelog. GitHub Releases provide some release communication, but the missing tests and documentation reduce maintainability and transparency for a package with substantial application code.

Release history

The package is only 47 days old but has 27 releases, with a median interval of about 21 hours, showing strong current publishing activity but limited maturity history.

Repo bus factor

One contributor made all 25 commits in the last three months, creating a genuine continuity risk. Organization ownership partly compensates because maintenance can potentially be handed off internally, but no second active contributor is evidenced.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is neutral for a small project, but it provides little evidence of external maintenance or review.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a transparency and hygiene gap rather than evidence of abandonment.