laravelgpt/data-breach

Licensing and documentation are in place, and the source matches the package. However, the project shows no follow-up activity and lacks security safeguards, making this release a risky long-term dependency.

Latest 2.0.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published within about 34 minutes on June 21, 2025, and none in the following 12 months. This indicates a stalled release history for a broad toolkit.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the past three months, consistent with the absence of recent registry releases. No compensating maintenance activity is shown.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption signal to offset the inactivity.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. That leaves the security-focused project without visible automated security coverage.

Security policy

The repository has no security policy. For a package presenting multiple security-related integrations, this is a meaningful transparency and maintenance gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

LaravelGPT

Direct Dependencies

Dependency	Last Release	Score
laravel/volt Version ^1.0	—	—
illuminate/http Version ^12.0	—	—
illuminate/mail Version ^12.0	—	—
illuminate/cache Version ^12.0	—	—
guzzlehttp/guzzle Version ^7.0	—	—