@openremote/or-attribute-history
OpenRemote attribute history
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): OpenRemote org packages consistently lack provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@material/data-table | AI (dependencies): @material/data-table is a well-known Google Material Components package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openremote/core | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@openremote/rest | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jsonpath-plus | AI (phantom-deps): Declared runtime dep; likely used transitively or in bundled output — stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): Declared runtime dep; likely used transitively or in bundled output — stable false positive. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 13 / 2 | |
| 1.24.0 | 13 / 1 | |
| 1.23.1 | 13 / 1 | |
| 1.23.0 | 13 / 1 | |
| 1.22.1 | 13 / 1 | |
| 1.22.0 | 13 / 1 | |
| 1.21.0 | 13 / 1 | |
| 1.6.5 | 8 / 2 | |
| 1.6.4 | 8 / 2 | |
| 1.6.3 | 8 / 2 | |
| 1.6.2 | 8 / 2 | |
| 1.6.0 | 8 / 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 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.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage 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.