Package Health/jpcaparas/laravel-faker-openai

jpcaparas/laravel-faker-openai

Tests, a readable README, and a matching repository make the package easy to inspect and integrate. There is no security policy, while the workflows have no dangerous sinks but use unpinned actions, limiting build reproducibility.

Latest 0.1.0

Packagist

57%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository are owned by the same individual account. This gives clear ownership, but does not provide the redundancy of organization backing.

Release history

The package has only one release, published about 20 months ago, with no releases in the last 12 months. This is a meaningful maintenance concern, though the repository remains available and is not archived.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push and single release, this indicates a real abandonment risk.

Repo issue activity

There were no new or closed issues and no pull requests in the last month, with two issues still open. This is consistent with a small project but provides little evidence of ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small package this is a modest transparency and maintenance gap rather than a severe risk.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

JP Caparas

Direct Dependencies

Dependency	Last Release	Score
nyholm/psr7 Version ^1.8	—	—
fakerphp/faker Version ^1.24	—	—
laravel/framework Version ^10.0 \|\| ^11.0	—	—
openai-php/laravel Version ^0.10.2	—	—
symfony/http-client Version ^7.2	—	—