carloscgo/shinobi

Release historydanger

The last release was in June 2018, with no releases in the following eight years; this is strong evidence of abandonment for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving current maintenance unproven.

Repo popularitycaution

The repository has zero stars and forks and one watcher, offering little supporting evidence of community review or ongoing use; popularity is only secondary evidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy, which makes vulnerability reporting and maintenance expectations less clear for a package handling application authorization.