@openremote/or-gauge
OpenRemote gauge
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:gaugeJS | AI (dependencies): gaugeJS is the canonical gauge chart library; its use is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@openremote/core | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@openremote/or-icon | AI (phantom-deps): Same-org scoped dep; stable false positive for this monorepo. | ai | |
| phantom-deps | phantom-dep:@openremote/or-translate | AI (phantom-deps): Same-org scoped dep; stable false positive for this monorepo. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): Declared in dependencies with matching @types devDep; likely used indirectly or in bundled output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate OpenRemote component; sparse metadata is a quality issue, not a spam indicator. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 7 / 2 | |
| 1.24.0 | 7 / 1 | |
| 1.23.1 | 7 / 1 | |
| 1.23.0 | 7 / 1 | |
| 1.22.1 | 7 / 1 | |
| 1.22.0 | 7 / 1 | |
| 1.21.0 | 7 / 1 | |
| 1.20.2 | 7 / 1 | |
| 1.20.1 | 7 / 1 | |
| 1.20.0 | 7 / 1 | |
| 1.19.0 | 7 / 1 | |
| 1.18.0 | 7 / 1 | |
| 1.17.3 | 7 / 1 | |
| 1.17.2 | 7 / 1 | |
| 1.17.1 | 7 / 1 | |
| 1.17.0 | 7 / 1 | |
| 1.16.1 | 7 / 1 | |
| 1.15.2 | 7 / 1 | |
| 1.15.1 | 7 / 1 | |
| 1.7.0 | 7 / 1 | |
| 1.6.5 | 7 / 1 | |
| 1.6.4 | 7 / 1 | |
| 1.6.3 | 7 / 1 | |
| 1.6.2 | 7 / 1 | |
| 1.6.0 | 7 / 1 |
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.