unit-testing/class-spy

Release historydanger

The package has only one release, published over 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, even for a small stable utility.

Repo commit activitydanger

There have been no commits or active maintainers in the last three months, and the repository was last pushed over 11 years ago. This is strong evidence that fixes and support may be unavailable.

Package file treecaution

The package contains only four files, including its manifest, README, and two PHP source files, and its repository tree matches the artifact. This is transparent but provides little visible project depth.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little community evidence to compensate for the lack of recent maintenance.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of a security problem.