tigress/form-viewer

This is a usable but relatively small and lightly evidenced package. Its 25 releases over 348 days, stable non-prerelease versioning, current non-archived repository, explicit GPL-3.0-or-later licensing, simple dependency profile, and absence of install-time scripts are positive. However, the repository shows no commits or active maintainers in the last three months despite frequent registry releases, has no tests, changelog, security policy, or security scanning, and does not match the package name or mention it in the README. These gaps create meaningful maintenance and provenance uncertainty, so adoption is reasonable only if the package is important enough to validate and monitor in your environment.

Latest 2026.03.13.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository records zero commits and zero active maintainers in the last three months, despite 25 registry releases in the last year. This mismatch is a meaningful maintenance and release-provenance concern.

Maintainers

Only one registry account, Rudy Mas, has publish access. The single-person publishing base is a resilience concern, though the linked repository also identifies the same individual as its owner.

Package scaffolding

A README is present, but neither the artifact nor repository contains tests or a changelog. For a package with application-facing controllers, services, views, and JavaScript, the lack of visible tests reduces maintenance confidence.

Project backing

The repository is owned by an individual account rather than an organization, providing no organizational backing or clear maintainer redundancy.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This may reflect a small, quiet project, but it provides no evidence of active user or maintainer collaboration.