get-tsconfig

Maintainerscaution

Only one registry account has publish access, which is a modest publishing continuity concern. However, repository activity shows four active contributors, partially compensating for the narrow registry access list.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is less formal backing for maintenance handoff. This is partly offset by four active recent contributors and frequent releases.

Repo toolingcaution

The repository uses TypeScript and npm build tooling, but reports no security scanning tools. The build setup is present; the missing scanning is a minor transparency gap.

Security policycaution

The repository has no published security policy. This does not indicate unsafe code, but it leaves vulnerability-reporting and response expectations undocumented.

Token permissionscaution

One workflow lacks top-level permissions and the release workflow grants top-level write access. These permissions are not inherently unsafe, but the declarations are less restrictive and explicit than ideal.