@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, so a manually published version cannot be tied back to a reviewed commit.
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 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.27.1 | 23 / 3 | |
| 1.27.0 | 23 / 3 | |
| 1.26.2 | 23 / 3 | |
| 1.26.1 | 23 / 3 | |
| 1.26.0 | 23 / 3 | |
| 1.25.0 | 23 / 3 | |
| 1.24.2 | 22 / 3 | |
| 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 | |
| 1.20.2 | 22 / 2 | |
| 1.20.1 | 22 / 2 | |
| 1.20.0 | 22 / 2 | |
| 1.19.0 | 22 / 2 | |
| 1.18.0 | 22 / 2 | |
| 1.17.3 | 22 / 2 | |
| 1.17.2 | 22 / 2 | |
| 1.17.1 | 22 / 2 | |
| 1.17.0 | 22 / 2 | |
| 1.16.1 | 22 / 2 | |
| 1.15.2 | 22 / 2 | |
| 1.15.1 | 22 / 2 | |
| 1.14.0 | 21 / 0 | |
| 1.13.1 | 21 / 0 | |
| 1.13.0 | 21 / 0 | |
| 1.12.3 | 21 / 0 | |
| 1.12.1 | 21 / 0 | |
| 1.12.0 | 21 / 0 | |
| 1.11.3 | 21 / 0 | |
| 1.11.2 | 21 / 0 | |
| 1.11.1 | 21 / 0 | |
| 1.11.0 | 21 / 0 |
v1.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
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.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.