mktemp

Project backingcaution

The repository is owned by an individual rather than an organization, so continuity depends primarily on that maintainer; this is partly offset by three active recent contributors.

Repo toolingcaution

The repository uses TypeScript, Vitest, and build scripts, demonstrating a structured build and test process; no security scanning tooling was detected, which is a modest transparency gap.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a hygiene gap rather than evidence of abandonment.

Token permissionscaution

All four workflows lack top-level permissions declarations, and none declares read-only permissions; although no top-level write access was observed, the missing explicit defaults reduce workflow transparency.