@unito/integration-debugger
The Unito Integration Debugger
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:react-blessed | AI (dependencies): react-blessed is a legitimate terminal UI library appropriate for a debugger CLI tool. | ai | |
| dependencies | unvetted-dep:@hookstate/core | AI (dependencies): hookstate is a known React state management library; consistent with react-blessed UI usage. | ai | |
| phantom-deps | phantom-dep:@oazapfts/runtime | AI (phantom-deps): @oazapfts/runtime is referenced in config (likely generated API client); stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Unito CLI tool; sparse README and no public repo URL are expected for private tooling, not spam indicators. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.34.0 | 15 / 17 | |
| 0.33.1 | 15 / 17 | |
| 0.33.0 | 15 / 17 | |
| 0.32.1 | 15 / 16 | |
| 0.32.0 | 15 / 16 | |
| 0.31.5 | 15 / 16 | |
| 0.31.4 | 15 / 16 | |
| 0.31.3 | 15 / 16 | |
| 0.31.2 | 15 / 16 | |
| 0.31.1 | 15 / 16 | |
| 0.31.0 | 15 / 16 | |
| 0.30.0 | 15 / 16 | |
| 0.29.1 | 15 / 16 | |
| 0.29.0 | 14 / 16 | |
| 0.28.12 | 14 / 16 | |
| 0.28.11 | 14 / 16 | |
| 0.28.10 | 14 / 16 | |
| 0.28.9 | 14 / 16 | |
| 0.28.8 | 14 / 16 | |
| 0.28.7 | 14 / 16 | |
| 0.28.6 | 15 / 16 | |
| 0.28.5 | 15 / 16 | |
| 0.28.4 | 15 / 16 | |
| 0.28.3 | 15 / 16 | |
| 0.28.2 | 15 / 16 | |
| 0.28.1 | 15 / 16 | |
| 0.28.0 | 15 / 16 | |
| 0.27.0 | 15 / 16 | |
| 0.26.9 | 15 / 16 | |
| 0.26.8 | 15 / 16 | |
| 0.26.7 | 15 / 16 | |
| 0.26.6 | 15 / 16 | |
| 0.26.4 | 16 / 17 | |
| 0.26.3 | 16 / 17 | |
| 0.26.2 | 16 / 17 | |
| 0.26.1 | 15 / 17 | |
| 0.26.0 | 15 / 17 | |
| 0.25.2 | 15 / 17 | |
| 0.25.1 | 15 / 17 | |
| 0.25.0 | 15 / 17 | |
| 0.24.3 | 14 / 17 | |
| 0.24.2 | 14 / 17 | |
| 0.24.0 | 14 / 19 | |
| 0.23.0 | 14 / 21 | |
| 0.22.10 | 14 / 21 | |
| 0.22.9 | 14 / 21 | |
| 0.22.8 | 14 / 21 | |
| 0.22.7 | 14 / 21 | |
| 0.22.6 | 14 / 21 |
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.