@openremote/or-dashboard-builder
OpenRemote Dashboard Builder
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; provenance not yet enabled but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:lodash.throttle | AI (phantom-deps): Same as lodash.debounce — types declared, used in bundle; stable false positive. | ai | |
| phantom-deps | phantom-dep:@openremote/core | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): Declared for type definitions in devDependencies; used transitively in bundled output, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openremote/or-asset-tree | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@openremote/or-attribute-picker | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@openremote/rest | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 22 / 3 | |
| 1.24.0 | 22 / 2 | |
| 1.23.1 | 22 / 2 | |
| 1.23.0 | 22 / 2 | |
| 1.22.1 | 22 / 2 | |
| 1.22.0 | 22 / 2 | |
| 1.21.0 | 22 / 2 |
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 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.