Package Health/schoolspider/spider-editor

schoolspider/spider-editor

Usable with caveats: the package is backed by a matching organization repository with tests, changelog, and automated tooling, but it has had no release for over two years and no commits in the last three months. Its low adoption and limited security documentation add maintenance risk.

Latest 0.0.11

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Dangerous workflows

One workflow uses pull_request_target, which deserves review because that trigger can expose elevated repository context. However, no untrusted checkout or script-injection pattern was detected, limiting the concern.

Release history

The latest release was over two years ago, with no releases in the last 12 months, despite eight releases during its initial development. This is a meaningful sign of slowed maintenance, though the repository is not archived.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates materially slowed maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these figures provide little supporting evidence of broad community review or adoption.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a package intended to be integrated into applications.