arachne/bootstrap

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. Package-level abandonment is a severe reason not to start a new dependency.

Release historydanger

The package has only three releases, and none in the last 12 months; its latest release was over ten years ago. This strongly indicates that maintenance has ended.

Repo commit activitydanger

The repository recorded no commits or active maintainers in the last three months, consistent with the package's long release gap. This materially increases abandonment risk.

Package file treecaution

The published artifact contains only composer.json and two source files, while the repository contains six files total. That is a very thin project footprint for a reusable package and provides little transparency.

Package scaffoldingcaution

The package has no README, while the repository also has no tests or changelog. Missing tests and changelog are normal packaging practice, but the absent consumer-facing README is a minor transparency gap for this library.