reavapay/jipange

The dependency set is modest, and the repository clearly matches the package and its organization owner. Consumer documentation and maintenance evidence are limited, so future support is less certain than the stable version suggests.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The published artifact has no README, while this Laravel integration exposes services, routes, migrations, and configuration that consumers need to understand; absent tests and a changelog are normal for the artifact and do not add concern.

Release history

This is the package's only release, published 189 days ago, so there is no demonstrated release cadence or history to establish sustained maintenance.

Repo commit activity

The repository had zero commits and zero active maintainers in the last 3 months, leaving no recent evidence of ongoing maintenance after the initial release.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected, reducing the project's automated security transparency.

Security policy

The repository has no security policy, so consumers are given no documented channel or process for reporting vulnerabilities.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Reava Pay

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^10.0\|^11.0\|^12.0	—	—
guzzlehttp/guzzle Version ^7.0	—	—
illuminate/support Version ^10.0\|^11.0\|^12.0	—	—
illuminate/database Version ^10.0\|^11.0\|^12.0	—	—