← Home

yargonaut

npm Repository Homepage

Decorate yargs content with chalk styles and figlet fonts

6
Versions
Apache-2.0
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

jjoselvnexdrew

Keywords

yargsfiglettextfontasciiansilocalefunchalkcolorterminalcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from nexdrew to jjoselv occurred in 2018; jjoselv is a long-standing account with clean history. No malicious changes in the diff. Judgment stable across versions. ai
maintainer-change maintainer-added AI (maintainer-change): jjoselv added as maintainer in 2018; long-standing account, no adverse findings. Legitimate transition. ai
maintainer-change maintainer-removed AI (maintainer-change): abg removed as part of the same 2018 maintainer transition; no evidence of hostile takeover. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.4 3 / 1
1.1.3 3 / 1
1.1.2 3 / 1
1.1.1 3 / 1
1.1.0 3 / 1
1.0.0 2 / 1

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

2 findings
HIGH Publisher changed: nexdrew → jjoselv (on 2018-07-04) provenance

This version was published by a different npm account than previous versions on 2018-07-04. 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.

v1.1.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: abg → nexdrew (on 2015-10-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-10-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.