naas/jpgraph

Tests, build tooling, security scanners, and a valid license provide useful baseline confidence. The workflows use unpinned actions, including one archived action, and the repository has no security policy, reducing transparency and build hygiene.

Latest 1.0.2

Packagist

56%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance record.

Release history

The package is about 20 months old but has only three releases, all clustered near the initial publication, with no releases in the last 12 months. This weakens evidence of ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, materially increasing maintenance and abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no pull requests are open. Together with the commit inactivity, this suggests limited current project engagement.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no external adoption signal.