esbuild-wasm

Repo bus factorcaution

One contributor made 31 of 34 recent commits, so development is highly concentrated. Three additional contributors were active, which provides some compensation but does not remove the single-maintainer continuity risk.

Repo package mentioncaution

The repository name does not match esbuild-wasm and its README does not mention the package explicitly, which leaves some uncertainty about package-to-repository ownership. The README does identify the repository as the esbuild project, making this consistent with a monorepo or companion-package relationship but not fully transparent.

Repo toolingcaution

The repository uses build tooling, but no security-scanning tools were detected. The active build setup compensates for some of this gap, though supply-chain review is less visible.

Security policycaution

No security policy was found in the repository. This is a transparency and vulnerability-reporting gap, although it is partly offset by the repository's active development and controlled workflows.

Token permissionscaution

Three workflows use read-only permissions and only the publishing workflow has top-level write permission. The write permission is limited to the publishing workflow, so this is a contained but notable privilege concern.