@gravity-ui/page-constructor
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a well-known, widely-used animation library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Gravity-UI ecosystem consistently publishes without Sigstore provenance; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:final-form | AI (phantom-deps): final-form is a declared dep used indirectly via react-final-form; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): monaco-editor declared dep, referenced via react-monaco-editor; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:github-buttons | AI (phantom-deps): github-buttons is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:react-transition-group | AI (phantom-deps): react-transition-group is a declared dep used transitively; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 8.13.0 | 25 / 94 | |
| 8.12.0 | 25 / 94 | |
| 8.11.0 | 25 / 94 | |
| 8.10.0 | 25 / 94 | |
| 8.9.0 | 24 / 95 | |
| 8.8.1 | 24 / 95 | |
| 8.8.0 | 24 / 95 | |
| 8.7.2 | 24 / 95 | |
| 8.7.0 | 24 / 95 | |
| 8.6.0 | 24 / 95 | |
| 8.5.0 | 24 / 95 | |
| 8.4.2 | 24 / 95 | |
| 8.4.1 | 24 / 95 | |
| 8.4.0 | 24 / 95 | |
| 8.3.0 | 24 / 95 |
v8.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.