validate.io-number

Release historydanger

The last release was in February 2015, with no releases in the past 11 years despite five historical releases. This is the strongest abandonment concern, although the package is a small, stable utility.

Repo commit activitydanger

There were zero commits and zero active maintainers in the past three months, with repository activity last observed in 2015. The stable scope partly explains this, but the maintenance gap remains significant.

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This is a transparency gap, but the package is a small artifact with no runtime dependencies and no install scripts.

Repo popularitycaution

The repository has two stars and one fork, providing little external adoption evidence. Popularity is supporting evidence only, so this modestly limits confidence rather than determining the verdict.

Repo toolingcaution

The repository uses Make for builds and tests, but reports no security scanning tools. The established build tooling is positive; the absent scanning is a modest transparency gap.