slacker775/knowbe4-kmsat-api

Release historydanger

The latest release was published about five years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk for a maintained API client.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided signal shows compensating recent maintenance.

Maintainerscaution

Only one registry maintainer is listed, leaving limited visible publishing capacity if that person becomes unavailable. The repository is user-owned rather than organization-backed, so there is no provided backing signal to offset this.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The build setup is a positive, while the missing scanning reduces maintenance transparency.

Security policycaution

The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a hygiene and response-capacity gap, not evidence of malicious behavior.