@gravity-ui/yagr
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yargs | AI (typosquat): Legitimate @gravity-ui scoped charting library; name similarity to yargs is coincidental. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 1 / 35 | |
| 4.14.1 | 1 / 35 | |
| 4.14.0 | 1 / 35 | |
| 4.13.9 | 1 / 35 | |
| 4.13.8 | 1 / 35 | |
| 4.13.6 | 1 / 35 | |
| 4.13.5 | 1 / 35 | |
| 4.13.4 | 1 / 35 | |
| 4.13.3 | 1 / 35 | |
| 4.13.2 | 1 / 35 | |
| 4.13.1 | 1 / 35 | |
| 4.13.0 | 1 / 35 | |
| 4.12.0 | 1 / 35 | |
| 4.11.0 | 1 / 35 | |
| 4.10.0 | 1 / 35 | |
| 4.9.2 | 1 / 35 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.