desicon/seal

This is a usable but still young package with an organization-backed repository, stable v1.0.2 release status, clear README, tests in both the artifact and repository, no install-time lifecycle scripts, and a safe read-only workflow permission profile. However, the package has only three releases over 106 days, no recorded commits or active maintainers in the last 3 months, no security policy or security scanning, and no adoption signals. The recent repository push and one merged pull request provide some evidence of ongoing activity, but the lack of measured commit activity makes maintenance continuity uncertain; depend on it with normal review and monitoring rather than treating it as mature infrastructure.

Latest v1.0.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 106 days old with three releases and a median release interval of about 53 days, so its maintenance history is still limited and long-term stability is not established.

Repo commit activity

The repository records zero commits and zero active maintainers during the last 3 months, a substantial maintenance-continuity concern despite the separately observed recent push.

Repo issue activity

There are no open issues or pull requests and one pull request was merged in the last month; this shows some interaction, although the absence of issue history limits evidence of sustained community maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these counters provide no external adoption or review signal for this young package.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured, leaving a security-hygiene gap for a package that handles telemetry and deployment reporting.