troika-three-text

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This limits publication transparency, but it is not by itself evidence of an unhealthy project.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, despite 69 open issues and 23 open pull requests. Recent commits and a current release reduce, but do not eliminate, the concern about issue responsiveness.

Repo package mentioncaution

The repository name does not match troika-three-text and its README does not mention the package. Although name mismatches can be normal in monorepos, the lack of any package mention makes the linkage worth treating as a transparency concern.

Repo toolingcaution

The project uses Rollup, Babel, and npm scripts, but no security-scanning tools were detected. The build setup is established while security automation is limited.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations and response guidance undocumented.