masitings/geni-api

Usable with caveats: the release is well-scaffolded, licensed, transparently backed by a matching repository, and has no deprecation or workflow-risk signals. However, it is only 1 day old with four releases, no measurable three-month commit history, and a single registry maintainer, so long-term stability is not yet demonstrated.

Latest v2.0.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Maintainers

Only one account has registry publish access. That is a limited publishing base for a user-owned project and increases continuity risk, although access records do not establish actual development activity.

Release history

The package is only 1 day old and has already published four releases, so its maintenance record and release process are not yet established. The rapid early cadence is not itself abandonment evidence, but it lowers maturity confidence.

Repo commit activity

The repository reports zero commits and zero active maintainers over the last 3 months. Because the project is only 1 day old, this mainly reflects insufficient history rather than demonstrated abandonment, but it leaves long-term maintenance unproven.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, and the package's age explains much of this, but there is no external adoption signal yet.

Security policy

The repository has no SECURITY policy. This is a transparency and vulnerability-reporting gap, though it is less severe than an unsafe workflow or missing source repository.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Rafi Bagaskara Halilintar

Direct Dependencies

Dependency	Last Release	Score
nikic/php-parser Version ^5.0	—	—
illuminate/contracts Version ^10.0\|^11.0\|^12.0\|^13.0	—	—
phpstan/phpdoc-parser Version ^2.0	—	—
spatie/laravel-package-tools Version ^1.16	—	—