deep-is

Build provenancecaution

No build provenance attestation or trusted-publisher metadata is present, so the release cannot be independently tied to a documented build process. This is a transparency limitation rather than evidence of maliciousness.

Maintainerscaution

Only one registry publishing maintainer is listed. That is not inherently unsafe for a small package, but it leaves limited visible redundancy for ongoing fixes or ownership changes.

Release historycaution

The package has five releases since April 2013, but none in the last 12 months; the latest release was published in September 2021. This indicates a long-maintained but now inactive release cadence.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. The repository is not archived, but current maintenance capacity is unclear.

Security policycaution

The repository has no security policy. For a small, inactive utility this is a transparency gap, although the package's lack of runtime dependencies limits the practical exposure.