surda/zebra

Its small dependency surface, clear MIT licensing, README, and tests make integration straightforward. The long release gaps and no recent commits suggest limited maintenance capacity; no security policy or scanning adds a smaller transparency concern.

Latest v2.1.0

Packagist

63%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only four releases since December 2022, with no release in the last 12 months and a median interval of about 14 months. This points to a slow maintenance cycle, though the latest release is established rather than experimental.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long release interval, this is evidence of limited recent maintenance.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but this provides little external evidence of broad adoption.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than a standalone adoption blocker.

Security policy

The repository has no security policy. For a package that sends data to network-connected printers, the missing disclosure process is a meaningful but limited transparency gap.