icss-utils

Release historydanger

The latest release was published nearly six years ago, with no releases in the last 12 months. The earlier 10-release history shows the project was once active but does not offset the current staleness.

Build provenancecaution

The release has no build attestation or trusted-publishing provenance, so consumers cannot independently verify how the artifact was produced. This lowers publishing transparency but is not severe on its own.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, indicating no recent maintenance capacity. This is partly softened by the repository not being archived.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while 14 pull requests remain open. This suggests limited current project activity and unresolved maintenance work.

Security policycaution

The linked repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, not evidence that the package is unsafe.