Package Health/amidesfahani/filament-tinyeditor

amidesfahani/filament-tinyeditor

This is a generally healthy and actively maintained release: it has 37 releases over roughly 2.9 years, 11 releases in the last 12 months, a stable non-prerelease major version, a non-deprecated registry status, a matching and README-referencing repository, and recent commits from two contributors. The main concerns are limited recent activity (only 2 commits in 3 months), no recent issue or pull-request closure activity, no repository security policy or security-scanning tooling, and no tests or changelog in the package or repository. These are meaningful transparency and maintenance gaps but do not outweigh the package's release cadence, active repository status, licensing, and evidence of a real maintained project.

Latest v5.0.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access, creating publishing continuity risk, although repository activity shows a second recent contributor and registry access is not evidence of actual maintenance capacity by itself.

Package scaffolding

A substantial README documents compatibility, installation, usage, and configuration, but neither the artifact nor repository contains tests or a changelog. The documentation compensates for part of the gap, while the lack of tests and release notes remains a modest hygiene concern.

Project backing

The repository is owned by a user rather than an organization, so there is no organization-level maintenance backing to offset the small registry maintainer base.

Repo commit activity

Only 2 commits were recorded in the last 3 months, showing limited recent development activity. This is partly offset by the package's strong release cadence and the fact that two maintainers were active.

Repo issue activity

There are 29 open issues and 4 open pull requests, but no new or closed issues and no merged pull requests in the last month. The backlog and lack of recent resolution indicate a modest maintenance concern.