← Home

human-id

npm Repository Homepage

Returns from a pool of 15m human-readable IDs

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

riennevaplus

Keywords

humanreadableididentifier

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Legitimate maintainer transfer to riennevaplus ~4.5 years ago; GitHub repo matches new publisher; 12 approved packages, 0 rejected. ai
maintainer-change maintainer-added AI (maintainer-change): riennevaplus is the established maintainer since 2021; GitHub repo is under their account. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous maintainer safebyte was replaced in a legitimate transfer ~4.5 years ago. ai
provenance publisher-changed AI (provenance): Publisher change from safebyte to riennevaplus occurred in 2021; well-established transition with matching GitHub ownership. ai

Versions (showing 12 of 12)

Version Deps Published
4.1.3 0 / 1
4.1.2 0 / 1
4.1.1 0 / 1
4.1.0 0 / 1
4.0.0 0 / 1
3.0.1 0 / 1
3.0.0 0 / 1
2.0.1 0 / 0
2.0.0 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v4.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (safebyte) were replaced by new maintainers (riennevaplus). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: safebyte → riennevaplus (on 2021-11-13) provenance

This version was published by a different npm account than previous versions on 2021-11-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.