mapsight/pulp-cache

This is a usable, transparently packaged release with a stable v1.1.0 version, MIT licensing, README/tests/changelog, a complete matching repository tree, no install-time scripts, and active organizational backing. The main concerns are its very young 75-day history, only three releases, zero recorded commits or active maintainers in the last three months, no repository security-scanning tooling, and minimal popularity; these suggest limited demonstrated maintenance depth rather than immediate unfitness. The recent repository push and organization-owned repository partially offset the inactivity signal, but adoption should still account for the package's short track record and thin observed activity.

Latest v1.1.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a thin publishing base; the organization-owned repository provides some compensating project backing, but does not establish a broad maintainer base.

Release history

The package is only 75 days old with three releases and a median release interval of about 38 days, so it has limited demonstrated maintenance history despite regular initial releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, a meaningful maintenance concern for a package whose release history is only 75 days old; the recent push provides limited counterevidence but does not demonstrate sustained activity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while open issue and pull-request counts are unknown; this supplies little evidence of community support or responsiveness.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is not required for a healthy small package, but these values provide no supporting evidence of community adoption.