Package Health

bnussbau/laravel-trmnl-blade

Version 3.3.1 appears healthy and reasonable to depend on: it is a stable, non-deprecated release with 22 releases over 455 days, 17 releases in the last 12 months, a recent repository push, documented licensing, repository tests and changelog coverage, and modest dependency complexity. The main risks are operational rather than abandonment-level: all recent commits come from one contributor, the package has very limited popularity, and several workflows grant write permissions or use pull_request_target. The package is therefore suitable for adoption with normal dependency and CI review, but it has less maintainer redundancy and repository security hardening than a mature, widely backed project.

Latest 3.3.1PackagistPackagist

82%

Total Score

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

70

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

70

Health Score Breakdown

Dangerous workflowscaution

Five workflows were analyzed; one uses pull_request_target, which can be a sensitive workflow context. No untrusted checkout or script-injection patterns were detected, reducing but not eliminating the workflow risk.

Lifecycle scriptscaution

The package uses a post-autoload-dump lifecycle script. This is an install-time execution surface that warrants review, although the signal does not show multiple or obviously excessive lifecycle hooks.

Maintainerscaution

Only one account has registry publish access. This is a limited publishing redundancy signal, and the repository evidence also shows a single active contributor, so release continuity depends heavily on one person.

Project backingcaution

The repository owner is the individual user bnussbau, not an organization. This does not indicate poor health by itself, but it means the single-maintainer and bus-factor concerns are not visibly mitigated by organizational backing.

Repo bus factorcaution

One contributor made all 6 commits in the last 3 months, with a 100% commit share. Because the owner is an individual user rather than an organization, there is no provided project-backing evidence to compensate for this concentration.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Benjamin Nussbaum

Direct Dependencies

DependencyLast ReleaseScore
illuminate/contracts
Version ^10.0||^11.0||^12.0||^13.0
—
—
spatie/laravel-package-tools
Version ^1.18
—
—

Weekly Downloads

Info

Last Published
1 month ago
Created
1 year 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