bitcodesa/msegat

Release historycaution

The package has six releases over about two years, but none in the last 12 months and the latest release was about one year ago. This is a meaningful maintenance concern for a dependency, though the release history is established rather than abandoned outright.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. That weakens evidence of current maintenance capacity.

Repo popularitycaution

The repository has one star, one fork, and one watcher, so there is little visible community validation or backup support. Popularity is supporting evidence only, so this is a minor concern alongside the inactive maintenance signals.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That modestly reduces assurance for a package intended to handle application integrations.

Security policycaution

The repository has no security policy, which reduces transparency about vulnerability reporting and maintenance response. This is a hygiene gap rather than evidence that the package is unsafe.