@esbuild/linux-s390x

Repo bus factorcaution

Four contributors were active, but one made 31 of 34 commits, or about 91%. The project is active, yet continuity depends heavily on one person.

Repo issue activitycaution

The repository remains active, but in the last month it closed only 1 issue, merged no pull requests, and received 8 new issues. This is a modest maintenance concern, partly offset by the recent commit and release activity.

Repo package mentioncaution

The repository name does not match this scoped binary package and its README does not mention the package, creating some ownership ambiguity. The package README explicitly points consumers to the esbuild repository, which partly explains the monorepo-style mismatch.

Repo toolingcaution

The project uses build tooling, but no security-scanning tools were detected. That is a transparency and hygiene gap, not evidence that the release is unsafe.

Security policycaution

No repository security policy was found. This makes vulnerability reporting less transparent, though the active project and provenance evidence reduce the practical concern.