jest-each

Repo package mentioncaution

The repository name does not match jest-each and its README does not mention the package, so the package-to-repository association is indirect and warrants caution. The monorepo context makes a name mismatch ordinary, but the absent README mention leaves the linkage less transparent.

Repo toolingcaution

The project uses established build tools including TypeScript, Babel, webpack, Vite, and npm scripts, but no security-scanning tools were detected. The tooling supports maintainability, while the missing scanner is a modest transparency gap.

Workflow auditcaution

All 11 workflows were analyzed successfully, all 48 action references are pinned, and no untrusted checkout or script-injection sink was found. The high-confidence use-trusted-publishing finding indicates registry publishing relies on a long-lived token, which is a supply-chain hygiene concern.