ansi

Release historydanger

The latest release was in January 2016, with no releases in the last 12 months. The package has an established history, but its release activity is too old to support confidence in ongoing maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating little current maintenance capacity.

Build provenancecaution

The release has no build attestation or trusted-publisher provenance, so consumers cannot verify how the artifact was produced. This is a supply-chain transparency gap, partly offset by the small and simple file tree.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, although two issues and three pull requests remain open. This suggests the project is largely inactive rather than actively resolving maintenance work.

Repo toolingcaution

The repository reports no build tooling or security scanning. That is a transparency and maintenance gap, though the package is a small, straightforward JavaScript artifact.