Package Health

devletes/filament-progress-bar

This is a reasonably healthy, actively published package with a matching source repository, a stable v1 release, clear documentation, changelog, licensing, repository tests, security policy, Dependabot, and safe workflow patterns. The main concerns are its young history of only 3 releases over 162 days, just 3 commits in the last 3 months, and all recent commits coming from one contributor; however, the repository is organization-owned, current, unarchived, and has good project and artifact hygiene. It is suitable to depend on with normal monitoring, though it has not yet demonstrated long-term maintenance depth.

Latest v1.2.0PackagistPackagist

78%

Total Score

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

75

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

80

Health Score Breakdown

Lifecycle scriptscaution

A post-autoload-dump lifecycle script is present. This is an install-time execution surface, but the signal provides no evidence that it is unsafe, so it is a modest transparency consideration rather than a severe health risk.

Release historycaution

The package is young at 162 days and has only 3 releases, with a median interval of about 81 days. This limits evidence of long-term maintenance maturity, although releases are still ongoing within the last 12 months.

Repo bus factorcaution

All 3 recent commits came from one contributor, creating a concentrated maintenance dependency. The organization-owned repository provides some ability to hand maintenance off, which reduces but does not eliminate this concern.

Repo commit activitycaution

The repository recorded 3 commits in the last 3 months, so development has not stopped, but the activity level is limited for establishing robust ongoing maintenance.

Token permissionscaution

Neither workflow declares top-level token permissions. Although no top-level write permissions are present, explicitly restricting workflow tokens would provide stronger CI hardening.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Devletes

Direct Dependencies

DependencyLast ReleaseScore
filament/filament
Version ^5.0
spatie/laravel-package-tools
Version ^1.16

Weekly Downloads

Info

Last Published
10 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