@hawtio/react
A Hawtio reimplementation based on TypeScript + 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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hawtio/camel-model-v4_10 | AI (dependencies): First-party Hawtio camel-model package aliased for multi-version support; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@hawtio/camel-model-v4_14 | AI (dependencies): First-party Hawtio camel-model package aliased for multi-version support; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Hawtio org package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:victory | AI (phantom-deps): victory is a declared runtime dep used via config/build tooling; phantom-dep heuristic fires but it's a legitimate dependency. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 20 / 31 | |
| 2.2.0 | 20 / 31 | |
| 2.1.0 | 20 / 31 | |
| 2.0.0 | 20 / 31 | |
| 1.13.0 | 19 / 31 | |
| 1.12.5 | 19 / 31 | |
| 1.12.3 | 19 / 31 | |
| 1.12.2 | 19 / 31 | |
| 1.12.1 | 19 / 31 | |
| 1.12.0 | 19 / 31 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.