@openremote/model
OpenRemote 3.x Model Types
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
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.27.1 | 0 / 0 | |
| 1.27.0 | 0 / 0 | |
| 1.26.2 | 0 / 0 | |
| 1.26.1 | 0 / 0 | |
| 1.26.0 | 0 / 0 | |
| 1.25.0 | 0 / 0 | |
| 1.24.2 | 0 / 0 | |
| 1.24.1 | 0 / 0 | |
| 1.24.0 | 0 / 0 | |
| 1.23.1 | 0 / 0 | |
| 1.23.0 | 0 / 0 | |
| 1.22.1 | 0 / 0 | |
| 1.22.0 | 0 / 0 | |
| 1.21.0 | 0 / 0 | |
| 1.20.2 | 0 / 0 | |
| 1.20.1 | 0 / 0 | |
| 1.20.0 | 0 / 0 | |
| 1.19.0 | 0 / 0 | |
| 1.18.0 | 0 / 0 | |
| 1.17.3 | 0 / 0 | |
| 1.17.2 | 0 / 0 | |
| 1.17.1 | 0 / 0 | |
| 1.17.0 | 0 / 0 | |
| 1.16.1 | 0 / 0 | |
| 1.15.2 | 0 / 0 | |
| 1.15.1 | 0 / 0 | |
| 1.14.0 | 0 / 0 | |
| 1.13.1 | 0 / 0 | |
| 1.13.0 | 0 / 0 | |
| 1.12.3 | 0 / 0 | |
| 1.12.1 | 0 / 0 | |
| 1.12.0 | 0 / 0 | |
| 1.11.3 | 0 / 0 | |
| 1.11.2 | 0 / 0 | |
| 1.11.1 | 0 / 0 | |
| 1.11.0 | 0 / 0 | |
| 1.10.0 | 0 / 1 | |
| 1.9.0 | 0 / 1 | |
| 1.8.1 | 0 / 1 | |
| 1.8.0 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.6.5 | 0 / 1 | |
| 1.6.4 | 0 / 1 | |
| 1.6.3 | 0 / 1 | |
| 1.6.2 | 0 / 1 | |
| 1.6.0 | 0 / 1 | |
| 1.5.0 | 0 / 1 | |
| 1.4.0 | 0 / 1 | |
| 1.3.5 | 0 / 1 | |
| 1.3.4 | 0 / 1 | |
| 1.3.3 | 0 / 1 | |
| 1.3.2 | 0 / 1 | |
| 1.3.1 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.4 | 0 / 1 | |
| 1.2.3 | 0 / 1 | |
| 1.2.2 | 0 / 1 | |
| 1.2.1 | 0 / 1 | |
| 1.2.0 | 0 / 1 |
v1.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.