plesk/stdio-react

Documentation, tests, licensing, and organizational ownership provide a solid foundation. The single release and absent recent commits limit confidence in ongoing maintenance, while workflow references remain unpinned.

Latest v2.6.1

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This release is the package's only release, published 559 days ago, with no releases in the last 12 months. That is a meaningful maintenance concern despite the package not being deprecated.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, and its latest push coincides with the sole release. This weakens evidence of ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was observed. The missing scanner is a modest transparency gap, not evidence of abandonment.

Security policy

The repository has no security policy. This leaves vulnerability-reporting expectations unclear, though the package's licensing, tests, and documentation compensate for some transparency concerns.

Workflow audit

The sole workflow has no dangerous triggers, untrusted checkouts, injection findings, or write permissions, but all 3 analyzed action references are unpinned. That is a supply-chain hygiene gap without a demonstrated exploit path.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Christian Lück

Direct Dependencies

Dependency	Last Release	Score
react/stream Version ^1.4	—	—
clue/term-react Version ^1.0 \|\| ^0.1.1	—	—
clue/utf8-react Version ^1.0 \|\| ^0.1	—	—
react/event-loop Version ^1.2	—	—