Package Health

blendbyte/coyotecert-laravel

This is a young but reasonably well-structured Laravel package with a stable v1.0.1 release, a matching source repository, repository tests, security policy, automated tooling, and no deprecation or dangerous workflow findings. The main concern is maintenance evidence: the repository shows zero commits and zero active maintainers in the last 3 months, while two pull requests remain unmerged; its short 140-day history and zero repository popularity also limit maturity evidence. Overall it appears usable, but adoption should include monitoring because sustained maintenance has not yet been demonstrated.

Latest v1.0.1PackagistPackagist

72%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

63

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

90

Health Score Breakdown

Repo commit activitydanger

The repository records zero commits and zero active maintainers over the last 3 months, despite the package's recent release and push metadata. This is the strongest maintenance concern because sustained implementation activity is not demonstrated.

Release historycaution

The package is only 140 days old with three releases and a median interval of about 70 days. This shows some release activity but provides limited long-term maintenance history.

Repo issue activitycaution

There are no open issues and two pull requests were opened in the last month, but none were merged. This indicates some engagement while leaving unresolved evidence about review and integration throughput.

Repo popularitycaution

The repository has zero stars, forks, and watchers. For a young package this is supporting evidence of limited adoption rather than a decisive health failure, but it provides little external validation.

Token permissionscaution

All four workflows lack top-level token permissions, and none declares top-level write access; however, the absence of explicit permissions weakens least-privilege clarity and should be tightened.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Blendbyte

Direct Dependencies

DependencyLast ReleaseScore
illuminate/support
Version ^12.0 || ^13.0
blendbyte/coyotecert
Version ^1.0
illuminate/contracts
Version ^12.0 || ^13.0

Weekly Downloads

Info

Last Published
18 days ago
Created
5 months ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform