tempest/validation

This release appears healthy and suitable for dependency use: it is actively released, stable, not deprecated, backed by a non-archived organization-owned repository, and has substantial recent commit activity from six contributors. The package is properly licensed and its source tree contains the expected implementation plus repository tests. The main reservations are that 85% of recent commits came from one contributor, the repository has no security scanning or security policy, and repository popularity is minimal; these are meaningful transparency and resilience gaps but are outweighed by the strong release cadence and active maintenance evidence.

Latest v3.19.2

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

Six contributors were active, but the leading contributor made 46 of 54 commits, an 85% share. The organization-owned repository provides some handoff capacity, but the concentration remains a resilience concern.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this provides little external validation and modestly lowers confidence in project maturity.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. This is a supply-chain hygiene gap, though it is not evidence of abandonment.

Security policy

The linked repository has no published security policy. This reduces vulnerability-reporting transparency and is a genuine maintenance-hygiene gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
tempest/intl Version 3.19.2	—	—
tempest/support Version 3.19.2	—	—
tempest/datetime Version 3.19.2	—	—
tempest/reflection Version 3.19.2	—	—
egulias/email-validator Version ^4.0.2	—	—