@gravity-ui/dynamic-forms
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): Established gravity-ui org package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 5.20.0 | 7 / 61 | |
| 5.19.1 | 7 / 61 | |
| 5.19.0 | 7 / 61 | |
| 5.18.0 | 6 / 62 | |
| 5.17.1 | 6 / 62 | |
| 5.16.0 | 6 / 62 | |
| 5.15.0 | 6 / 62 | |
| 5.14.0 | 6 / 62 | |
| 5.13.2 | 6 / 62 | |
| 5.13.1 | 6 / 62 | |
| 5.13.0 | 6 / 62 | |
| 5.12.1 | 6 / 62 | |
| 5.12.0 | 6 / 62 | |
| 5.11.0 | 6 / 62 | |
| 5.10.1 | 6 / 62 | |
| 5.10.0 | 6 / 62 | |
| 5.9.4 | 6 / 62 | |
| 5.9.3 | 6 / 62 | |
| 5.9.2 | 6 / 62 | |
| 5.9.1 | 6 / 62 | |
| 5.9.0 | 6 / 62 | |
| 5.8.1 | 6 / 62 | |
| 5.8.0 | 6 / 62 | |
| 5.7.0 | 6 / 62 | |
| 5.6.0 | 6 / 62 | |
| 5.5.0 | 6 / 62 | |
| 5.4.1 | 6 / 62 | |
| 5.4.0 | 6 / 62 | |
| 5.3.0 | 6 / 62 | |
| 5.2.0 | 6 / 61 | |
| 5.1.0 | 6 / 60 | |
| 5.0.0 | 6 / 60 |
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.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.
v5.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.