@openremote/or-vaadin-components
Vaadin Components packaged as components aligned with the OpenRemote design system
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/value-input-provider.js | AI (source-diff): Minified TypeScript build output with readable Lit/Vaadin logic; not obfuscated malware. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/button | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/dialog | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/select | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/text-area | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/date-picker | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/radio-group | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/icons | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/number-field | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/checkbox-group | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/password-field | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/date-time-picker | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vaadin/multi-select-combo-box | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): OpenRemote org does not use Sigstore provenance; consistent across their 162 published versions. | ai | |
| dependencies | unvetted-dep:@vaadin/time-picker | AI (dependencies): Legitimate Vaadin UI component; stable dependency for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 19 / 0 | |
| 1.24.0 | 19 / 0 | |
| 1.23.1 | 19 / 0 | |
| 1.23.0 | 19 / 0 | |
| 1.22.1 | 19 / 0 | |
| 1.22.0 | 19 / 0 | |
| 1.21.0 | 19 / 0 | |
| 1.20.2 | 19 / 0 | |
| 1.20.1 | 19 / 0 | |
| 1.20.0 | 19 / 0 | |
| 1.19.0 | 19 / 0 | |
| 1.18.0 | 19 / 0 | |
| 1.17.3 | 11 / 0 | |
| 1.17.2 | 11 / 0 | |
| 1.17.1 | 11 / 0 | |
| 1.17.0 | 11 / 0 | |
| 1.16.1 | 11 / 0 | |
| 1.15.2 | 10 / 0 | |
| 1.15.1 | 10 / 0 | |
| 1.14.0 | 10 / 0 | |
| 1.13.1 | 10 / 0 |
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 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.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.
v1.20.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.