@synerise/ds-form
Form UI Component for the Synerise 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, 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): Synerise DS packages consistently lack provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@synerise/ds-cruds | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai | |
| dependencies | unvetted-dep:@synerise/ds-input | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai | |
| dependencies | unvetted-dep:@synerise/ds-button | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai | |
| dependencies | unvetted-dep:@synerise/ds-icon | AI (dependencies): Internal sibling dep from same Synerise DS monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@synerise/ds-typography | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai | |
| dependencies | unvetted-dep:@synerise/ds-autocomplete | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai | |
| dependencies | unvetted-dep:@synerise/ds-divider | AI (dependencies): Internal sibling dep from same Synerise DS monorepo. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.2.22 | 7 / 0 | |
| 1.2.21 | 7 / 0 | |
| 1.2.20 | 7 / 0 | |
| 1.2.19 | 7 / 0 | |
| 1.2.18 | 7 / 0 | |
| 1.2.17 | 7 / 0 | |
| 1.2.16 | 7 / 0 | |
| 1.2.15 | 7 / 0 | |
| 1.2.14 | 7 / 0 | |
| 1.2.13 | 7 / 0 | |
| 1.2.12 | 7 / 0 | |
| 1.2.11 | 7 / 0 | |
| 1.2.10 | 7 / 0 | |
| 1.2.9 | 7 / 0 | |
| 1.2.8 | 7 / 0 | |
| 1.2.7 | 7 / 0 | |
| 1.2.6 | 7 / 0 | |
| 1.2.5 | 7 / 0 | |
| 1.2.4 | 7 / 0 | |
| 1.2.3 | 7 / 0 | |
| 1.2.2 | 7 / 0 | |
| 1.2.1 | 7 / 0 | |
| 1.2.0 | 7 / 0 | |
| 1.1.27 | 7 / 0 | |
| 1.1.26 | 7 / 0 | |
| 1.1.25 | 7 / 0 | |
| 1.1.24 | 7 / 0 | |
| 1.1.23 | 7 / 0 | |
| 1.1.22 | 7 / 0 | |
| 1.1.21 | 7 / 0 | |
| 1.1.20 | 7 / 0 | |
| 1.1.19 | 7 / 0 | |
| 1.1.18 | 7 / 0 | |
| 1.1.17 | 7 / 0 | |
| 1.1.16 | 7 / 0 | |
| 1.1.15 | 7 / 0 | |
| 1.1.14 | 7 / 0 | |
| 1.1.13 | 7 / 0 | |
| 1.1.12 | 7 / 0 | |
| 1.1.11 | 7 / 0 | |
| 1.1.10 | 7 / 0 | |
| 1.1.9 | 7 / 0 | |
| 1.1.8 | 7 / 0 | |
| 1.1.7 | 7 / 0 | |
| 1.1.6 | 7 / 0 | |
| 1.1.5 | 7 / 0 | |
| 1.1.4 | 7 / 0 | |
| 1.1.3 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.27 | 8 / 0 | |
| 1.0.26 | 8 / 0 | |
| 1.0.25 | 8 / 0 | |
| 1.0.24 | 8 / 0 | |
| 1.0.23 | 8 / 0 | |
| 1.0.22 | 8 / 0 | |
| 1.0.21 | 8 / 0 | |
| 1.0.20 | 8 / 0 | |
| 1.0.19 | 8 / 0 | |
| 1.0.18 | 8 / 0 | |
| 1.0.17 | 8 / 0 | |
| 1.0.16 | 8 / 0 | |
| 1.0.15 | 8 / 0 | |
| 1.0.14 | 8 / 0 | |
| 1.0.13 | 8 / 0 | |
| 1.0.12 | 8 / 0 | |
| 1.0.11 | 8 / 0 | |
| 1.0.10 | 8 / 0 | |
| 1.0.9 | 8 / 0 | |
| 1.0.8 | 8 / 0 | |
| 1.0.7 | 8 / 0 | |
| 1.0.6 | 8 / 0 | |
| 1.0.5 | 8 / 0 | |
| 1.0.4 | 8 / 0 | |
| 1.0.3 | 8 / 0 | |
| 1.0.2 | 8 / 0 | |
| 1.0.1 | 8 / 0 | |
| 1.0.0 | 8 / 0 |
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.