@git-diff-view/react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@git-diff-view/utils | AI (dependencies): Same-org monorepo sibling package, version-locked; not a third-party unvetted dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an internal scoped sibling package, not an external addition. | ai | |
| phantom-deps | phantom-dep:@git-diff-view/utils | AI (phantom-deps): Same org scope, likely re-exported internally. | ai | |
| dependencies | unvetted-dep:@types/hast | AI (dependencies): @types/hast is a TypeScript type definition package; no runtime risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): Type-only package loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:fast-diff | AI (phantom-deps): Referenced in config/bundler context; stable false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 7 / 5 | |
| 0.1.6 | 7 / 5 | |
| 0.1.5 | 7 / 5 | |
| 0.1.4 | 7 / 5 | |
| 0.1.3 | 7 / 5 | |
| 0.1.2 | 7 / 5 | |
| 0.1.1 | 7 / 5 | |
| 0.1.0 | 7 / 5 | |
| 0.0.40 | 7 / 5 | |
| 0.0.39 | 7 / 5 | |
| 0.0.38 | 7 / 5 | |
| 0.0.37 | 7 / 5 | |
| 0.0.36 | 7 / 5 | |
| 0.0.35 | 7 / 5 | |
| 0.0.34 | 7 / 5 | |
| 0.0.33 | 7 / 5 | |
| 0.0.32 | 7 / 5 | |
| 0.0.31 | 7 / 5 | |
| 0.0.30 | 7 / 5 | |
| 0.0.29 | 7 / 5 | |
| 0.0.28 | 7 / 5 | |
| 0.0.27 | 7 / 5 | |
| 0.0.26 | 7 / 5 | |
| 0.0.25 | 7 / 5 | |
| 0.0.24 | 7 / 7 | |
| 0.0.23 | 8 / 7 | |
| 0.0.22 | 7 / 7 | |
| 0.0.21 | 7 / 7 | |
| 0.0.20 | 7 / 7 | |
| 0.0.19 | 7 / 7 | |
| 0.0.18 | 7 / 7 | |
| 0.0.17 | 7 / 7 | |
| 0.0.16 | 6 / 6 | |
| 0.0.15 | 6 / 6 | |
| 0.0.14 | 6 / 6 | |
| 0.0.9 | 4 / 7 | |
| 0.0.8 | 4 / 7 | |
| 0.0.7 | 4 / 7 | |
| 0.0.6 | 4 / 7 | |
| 0.0.5 | 4 / 7 | |
| 0.0.3 | 4 / 7 | |
| 0.0.2 | 4 / 7 | |
| 0.0.1 | 5 / 5 |
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.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.