@webitel/ui-datalist
Toolkit for building data lists in webitel ui system
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/modules/card/composables/useNestedCardComponent.d.ts | AI (source-diff): Long lines in .d.ts files are caused by deeply nested TypeScript generics, not obfuscation. Stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; CI/CD publishing is the expected pattern for this package going forward. | ai | |
| provenance | no-provenance | AI (provenance): Webitel org packages consistently lack provenance; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@webitel/styleguide | AI (phantom-deps): Same org scope; phantom-dep heuristic false positive for intra-org packages. | ai | |
| phantom-deps | phantom-dep:@vuelidate/validators | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 52 of 152)
| Version | Deps | Published |
|---|---|---|
| 1.0.53 | 8 / 24 | |
| 1.0.52 | 8 / 24 | |
| 1.0.51 | 8 / 24 | |
| 1.0.50 | 8 / 24 | |
| 1.0.48 | 8 / 24 | |
| 1.0.47 | 7 / 24 | |
| 1.0.46 | 6 / 24 | |
| 1.0.45 | 6 / 24 | |
| 1.0.44 | 6 / 24 | |
| 1.0.43 | 6 / 24 | |
| 1.0.42 | 6 / 24 | |
| 1.0.41 | 6 / 24 | |
| 1.0.40 | 6 / 24 | |
| 1.0.39 | 6 / 24 | |
| 1.0.38 | 6 / 24 | |
| 1.0.37 | 6 / 24 | |
| 1.0.36 | 6 / 24 | |
| 1.0.35 | 4 / 23 | |
| 1.0.34 | 4 / 23 | |
| 1.0.33 | 4 / 23 | |
| 1.0.32 | 4 / 23 | |
| 1.0.31 | 4 / 23 | |
| 1.0.30 | 4 / 23 | |
| 1.0.29 | 4 / 23 | |
| 1.0.28 | 4 / 23 | |
| 1.0.27 | 4 / 23 | |
| 1.0.26 | 4 / 23 | |
| 1.0.25 | 4 / 23 | |
| 1.0.24 | 4 / 23 | |
| 1.0.23 | 4 / 23 | |
| 1.0.22 | 4 / 23 | |
| 1.0.21 | 4 / 23 | |
| 1.0.20 | 4 / 23 | |
| 1.0.19 | 4 / 23 | |
| 1.0.18 | 4 / 23 | |
| 1.0.17 | 4 / 23 | |
| 1.0.16 | 4 / 23 | |
| 1.0.15 | 4 / 23 | |
| 1.0.14 | 4 / 23 | |
| 1.0.13 | 4 / 23 | |
| 1.0.12 | 4 / 23 | |
| 1.0.11 | 3 / 23 | |
| 1.0.9 | 3 / 23 | |
| 1.0.8 | 3 / 23 | |
| 1.0.7 | 3 / 23 | |
| 1.0.6 | 3 / 23 | |
| 1.0.5 | 3 / 23 | |
| 1.0.4 | 3 / 23 | |
| 1.0.3 | 3 / 23 | |
| 1.0.2 | 3 / 23 | |
| 1.0.1 | 3 / 23 | |
| 1.0.0 | 3 / 23 |
v1.0.34
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.0.33
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.0.32
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.0.31
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.0.30
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.0.29
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.0.28
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.0.27
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.0.26
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.0.25
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.0.24
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.0.23
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.0.22
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.0.21
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.0.20
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.0.19
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.0.18
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.0.17
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.0.16
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.0.15
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.0.14
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.0.13
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.0.12
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.0.11
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.0.9
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.0.8
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.0.7
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.0.6
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.0.5
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.0.4
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.0.3
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.0.2
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.0.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.0.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.