leafs/vite

leafs/vite v5.0.2 appears usable and generally healthy to depend on: it is not deprecated or archived, has a stable major release, a correctly matching repository, tests, licensing, build tooling, and recent release and commit activity. The main concerns are that all seven commits in the last three months came from one contributor, the repository has no security scanning or security policy, and its popularity is minimal; these warrant some caution but do not outweigh the evidence of active maintenance and organization backing.

Latest v5.0.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all seven recent commits, creating a single-person bus-factor risk. Organization ownership partly compensates because maintenance can potentially be handed off.

Repo popularity

The repository has zero stars, forks, and watchers, indicating very limited visible adoption; popularity is supporting evidence rather than a standalone health verdict.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected; the missing scanning is a genuine security-hygiene gap, though it does not by itself establish poor package health.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response procedures.

Token permissions

The only workflow lacks top-level token permissions. Although no write permissions were explicitly declared, the absence of a restrictive declaration is a workflow-hardening gap.