@openremote/or-services
OpenRemote services related UI components
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:@openremote/rest | AI (phantom-deps): Monorepo pattern; @openremote org packages declare shared deps. | ai | |
| phantom-deps | phantom-dep:@openremote/or-mwc-components | AI (phantom-deps): Monorepo pattern; @openremote org packages declare shared deps. | ai | |
| phantom-deps | phantom-dep:@openremote/core | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for peer/re-export patterns. | ai | |
| phantom-deps | phantom-dep:@openremote/or-translate | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for peer/re-export patterns. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 7 / 1 | |
| 1.24.0 | 7 / 0 | |
| 1.23.1 | 7 / 0 | |
| 1.23.0 | 7 / 0 | |
| 1.22.1 | 7 / 0 | |
| 1.22.0 | 7 / 0 | |
| 1.21.0 | 7 / 0 | |
| 1.20.2 | 7 / 0 | |
| 1.20.1 | 7 / 0 | |
| 1.20.0 | 7 / 0 | |
| 1.19.0 | 7 / 0 | |
| 1.18.0 | 7 / 0 | |
| 1.17.3 | 7 / 0 | |
| 1.17.2 | 7 / 0 | |
| 1.17.1 | 7 / 0 | |
| 1.17.0 | 7 / 0 | |
| 1.16.1 | 7 / 0 | |
| 1.15.2 | 7 / 0 | |
| 1.15.1 | 7 / 0 | |
| 1.14.0 | 7 / 0 | |
| 1.13.1 | 7 / 0 | |
| 1.13.0 | 7 / 0 | |
| 1.12.3 | 7 / 0 | |
| 1.12.1 | 7 / 0 | |
| 1.12.0 | 7 / 0 | |
| 1.11.3 | 7 / 0 | |
| 1.11.2 | 7 / 0 | |
| 1.11.1 | 7 / 0 | |
| 1.11.0 | 7 / 0 | |
| 1.10.0 | 8 / 1 | |
| 1.9.0 | 8 / 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.