yargs-unparser
Converts back a yargs argv object to its original array form
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transfer from original author to bcoe (yargs org maintainer). Package now lives under github.com/yargs. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are yargs org members; legitimate organizational transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original solo maintainer removed as part of transfer to yargs org; expected. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 4 / 7 | |
| 1.6.4 | 5 / 7 | |
| 1.6.3 | 5 / 7 | |
| 1.6.1 | 5 / 7 | |
| 1.6.0 | 3 / 10 | |
| 1.5.1 | 3 / 10 | |
| 1.5.0 | 3 / 10 | |
| 1.4.0 | 3 / 10 | |
| 1.3.0 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.3 | 2 / 6 | |
| 1.0.2 | 2 / 6 | |
| 1.0.1 | 2 / 6 | |
| 1.0.0 | 2 / 6 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
2 findingsThis version was published by a different npm account than previous versions on 2018-12-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.