qifen/casbin

Release historydanger

The latest release was 4 years and 6 months ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk for an integration package.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the stale release history. There is no provided maintenance activity to offset this gap.

Licensecaution

The package declares MIT, but the detected LICENSE file is Apache-2.0. A license is present, but the mismatch creates avoidable uncertainty about the terms covering the release.

Repo popularitycaution

The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no community signal to compensate for stale maintenance.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security-scanning tools are configured. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.