fsi/cache

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement identified; this is a severe adoption risk even though the source repository is not archived.

Release historydanger

The last registry release was about 13 years ago, with no releases in the last 12 months. This strongly indicates the package is no longer maintained for current consumers.

Repo commit activitydanger

The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap and abandoned status.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. This is a modest transparency and maintenance gap, not evidence of malicious behavior.

Repository archivedcaution

The repository is not archived, which is a positive distinction, but it was last pushed about nine years ago; the stale repository still raises abandonment concerns.