rais/momo-suite

The README explains installation and configuration clearly, with MIT licensing, a small runtime dependency set, and no install-time scripts. The repository has no security policy or scanning evidence, so ongoing oversight is limited.

Latest 1.0.0

Packagist

54%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so there is no organizational backing signal to offset the thin maintenance evidence.

Release history

This is the package's only release, published about 16 months ago, with no releases in the last 12 months. That provides little evidence of an established maintenance cycle.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with a single release, this raises the risk that fixes and updates may not arrive promptly.

Repo popularity

The repository has 0 stars, 1 fork, and 1 watcher, indicating limited visible adoption. Popularity is supporting evidence only, so this is a modest concern rather than a decisive failure.

Repo tooling

Composer is used for builds, but no security scanning tool is configured. The build setup is appropriate, while the missing scanning evidence modestly reduces transparency.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Rais

Direct Dependencies

Dependency	Last Release	Score
guzzlehttp/guzzle Version ^7.2	—	—
illuminate/console Version ^8.0 \|\| ^9.0 \|\| ^10.0 \|\| ^11.0	—	—
illuminate/support Version ^8.0 \|\| ^9.0 \|\| ^10.0 \|\| ^11.0	—	—
illuminate/contracts Version ^8.0 \|\| ^9.0 \|\| ^10.0 \|\| ^11.0	—	—