@esbuild/linux-ia32

Repo bus factorcaution

The leading contributor made 31 of 34 recent commits, so maintenance is heavily concentrated even though three other contributors were active.

Repo package mentioncaution

The repository name does not match this platform-specific package and its README does not mention the exact package, which weakens package-to-repository traceability; the README does identify the repository as the parent esbuild project, partly compensating for the subpackage naming difference.

Repo toolingcaution

The project uses build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of abandonment.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting and response expectations undocumented.

Workflow auditcaution

All four workflows were analyzed and all action references are pinned, with no untrusted checkout or script-injection paths. However, one workflow has top-level write permissions, a high-severity but low-confidence cache finding, an archived action, and repeated high-confidence ad hoc package installs, creating workflow hygiene concerns.