compwright/disguz

Release historydanger

Only two releases were published, with the latest in December 2014 and none in the last 12 months. Nearly 12 years without a release is strong evidence of abandonment for a maintained API client.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with its last push having occurred in 2014. This leaves little evidence of ongoing maintenance.

Repo popularitycaution

The repository has only 1 star, 1 fork, and 1 watcher, providing little community evidence or backup for a package that has not been maintained for years.

Repo toolingcaution

Composer is used for the build, which supports reproducible package management, but no security scanning tooling is present. That reduces maintenance assurance for an old API client.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a secondary transparency gap rather than evidence of a specific vulnerability.