kamerk22/ipfuscator

The package includes a clear MIT license, usage documentation, repository tests, and no install-time scripts. Its small dependency footprint and matching source repository help, but security scanning is absent and the project has little activity evidence.

Latest v1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months, while the repository was last pushed in December 2018. This is the strongest evidence of abandonment risk.

Project backing

The package and repository are both owned by the same individual account, providing consistent ownership context. Individual backing also means there is no organization-level maintainer capacity shown here.

Release history

Only one release exists, published in December 2018, with no releases in the last 12 months. This indicates a maturely aged but potentially abandoned package and materially lowers confidence in ongoing maintenance.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull-request activity. This is consistent with a quiet project but does not by itself distinguish resolution from abandonment.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanner is a hygiene gap, not evidence that the package is unsafe or unmaintained on its own.