@gravity-ui/blog-constructor
Gravity UI Blog 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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted org bot publisher with strong track record; dormancy likely reflects org release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@gravity-ui/components | AI (dependencies): Same gravity-ui org dependency; consistent across package history. | ai | |
| dependencies | unvetted-dep:@gravity-ui/gulp-utils | AI (dependencies): Same gravity-ui org build utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established gravity-ui org package; lack of provenance is consistent across their releases. | ai | |
| phantom-deps | phantom-dep:@gravity-ui/gulp-utils | AI (phantom-deps): Same-org build utility; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic fires on config references, stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 10.1.0 | 11 / 67 | |
| 10.0.4 | 10 / 68 | |
| 10.0.2 | 10 / 68 | |
| 10.0.1 | 10 / 68 | |
| 10.0.0 | 10 / 68 | |
| 9.1.2 | 10 / 68 | |
| 9.1.1 | 10 / 68 | |
| 9.1.0 | 10 / 68 | |
| 9.0.0 | 10 / 68 | |
| 8.5.4 | 10 / 68 | |
| 8.5.3 | 10 / 68 | |
| 8.5.2 | 10 / 68 | |
| 8.5.1 | 10 / 68 |
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.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.
v8.5.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.
v8.5.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.