y0lk/jobby

The repository has seen no commits or active maintainers for three months, following a burst of 37 releases on one day. Documentation, tests, licensing, and read-only workflow permissions are solid, but unpinned actions and no security policy reduce transparency.

Latest v4.0.0

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months. For a package released about five months ago, that is a meaningful maintenance and abandonment concern.

Project backing

The package and repository are owned by the same individual account, so the source appears aligned with the package rather than being backed by an organization. This provides direct ownership clarity but limited evidence of institutional continuity.

Release history

The package has 37 releases in 151 days, but all were published on the same day with a median interval of zero days. That burst gives less evidence of a sustained release process.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external adoption signal for a young fork.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency gap, not evidence that the package is unsafe.