jimbojsb/dataslurp

The package has only a 12-character README, no visible security policy, and no recent project activity. Its small dependency set and matching repository reduce complexity, but the long maintenance gap makes adoption a liability.

Latest v0.2.9

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in November 2017, with no releases in the last 12 months. Eleven releases show some historical activity, but the roughly eight-year gap is a strong abandonment concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Package scaffolding

The package includes a README, but it is only 12 characters long and provides almost no consumer guidance. Missing tests and a changelog are normal for a published artifact and are not treated as gaps here.

Repo popularity

The repository has zero stars, two forks, and one watcher, offering little supporting evidence of broad use or community oversight. Popularity is only supporting evidence, so this does not determine the score alone.

Security policy

The linked repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a secondary concern beside the much stronger evidence of inactivity.