@git-diff-view/file
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:vite | AI (typosquat): Scoped monorepo package; Levenshtein match to 'vite' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:fast-diff | AI (phantom-deps): fast-diff is a declared runtime dependency; phantom-dep heuristic misfires on indirect usage patterns. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 5 / 2 | |
| 0.1.6 | 5 / 2 | |
| 0.1.5 | 5 / 2 | |
| 0.1.4 | 5 / 2 | |
| 0.1.3 | 5 / 2 | |
| 0.1.2 | 5 / 2 | |
| 0.1.1 | 5 / 2 | |
| 0.1.0 | 5 / 2 | |
| 0.0.40 | 5 / 2 | |
| 0.0.39 | 5 / 2 | |
| 0.0.38 | 5 / 2 | |
| 0.0.37 | 5 / 2 | |
| 0.0.36 | 5 / 2 | |
| 0.0.35 | 5 / 2 | |
| 0.0.34 | 5 / 2 | |
| 0.0.33 | 5 / 2 | |
| 0.0.32 | 5 / 2 | |
| 0.0.31 | 5 / 2 | |
| 0.0.30 | 5 / 2 | |
| 0.0.29 | 5 / 2 | |
| 0.0.28 | 5 / 2 | |
| 0.0.27 | 5 / 2 | |
| 0.0.26 | 5 / 2 | |
| 0.0.25 | 5 / 2 | |
| 0.0.24 | 5 / 2 | |
| 0.0.23 | 5 / 2 | |
| 0.0.22 | 5 / 2 | |
| 0.0.21 | 5 / 2 | |
| 0.0.20 | 5 / 2 | |
| 0.0.19 | 5 / 2 | |
| 0.0.18 | 5 / 2 | |
| 0.0.17 | 5 / 2 | |
| 0.0.16 | 4 / 2 | |
| 0.0.15 | 4 / 2 | |
| 0.0.14 | 4 / 2 | |
| 0.0.13 | 2 / 3 | |
| 0.0.12 | 2 / 3 |
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.