Package Health/jeroen/file-fetcher-cache

jeroen/file-fetcher-cache

Usable with caveats: the package is licensed, tested, clearly documented, and its repository is active enough to support a small stable library. Its release history is sparse, no commits were recorded in the last three months, and it relies on one maintainer without a security policy.

Latest 1.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. That is a thin publishing base for long-term continuity, although the linked project is owned by the same individual and is not presented as organization-backed.

Project backing

The registry namespace and repository are tied to the same individual owner, which supports provenance, but there is no organization backing to broaden maintenance capacity.

Release history

The package has existed for about 7 years and 8 months but has only three releases, with a median interval of about 3 years and 6 months. One release in the last 12 months shows some continued maintenance, but the cadence is sparse.

Repo commit activity

No commits or active maintainers were recorded in the last three months. Combined with the sparse release history, this raises maintenance and abandonment concerns even though the repository was pushed recently.

Security policy

The repository has no SECURITY.md or other declared security policy, leaving vulnerability reporting and response expectations unclear.