@openremote/or-log-viewer
OpenRemote syslog viewer
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a declared dep used in build/config context for this package; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established OpenRemote org package; no provenance is a process gap, not a security risk for this publisher. | ai | |
| phantom-deps | phantom-dep:@openremote/core | AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly. Stable false positive for this package family. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 10 / 1 | |
| 1.24.0 | 10 / 0 | |
| 1.23.1 | 10 / 0 | |
| 1.23.0 | 10 / 0 | |
| 1.22.1 | 10 / 0 | |
| 1.22.0 | 10 / 0 | |
| 1.21.0 | 10 / 0 | |
| 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.