@gravitee/ui-schematics
Gravitee.io - UI Schematics
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
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 17.9.0 | 1 / 2 | |
| 17.8.0 | 1 / 2 | |
| 17.7.5 | 1 / 2 | |
| 17.7.4 | 1 / 2 | |
| 17.7.3 | 1 / 2 | |
| 17.7.2 | 1 / 2 | |
| 17.7.1 | 1 / 2 | |
| 17.7.0 | 1 / 2 | |
| 17.6.1 | 1 / 2 | |
| 17.6.0 | 1 / 2 | |
| 17.5.0 | 1 / 2 | |
| 17.4.0 | 1 / 2 | |
| 17.3.0 | 1 / 2 | |
| 17.2.0 | 1 / 2 | |
| 17.1.0 | 1 / 2 | |
| 17.0.0 | 1 / 2 | |
| 16.4.2 | 1 / 2 | |
| 16.4.1 | 1 / 2 | |
| 16.4.0 | 1 / 2 | |
| 16.3.0 | 1 / 2 | |
| 16.2.5 | 1 / 2 | |
| 16.2.4 | 1 / 2 | |
| 16.2.3 | 1 / 2 | |
| 16.2.2 | 1 / 2 | |
| 15.13.1 | 1 / 2 |
v17.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.