@diia-inhouse/scaffold
This repository provides an overview over the flagship product [**Diia**](https://diia.gov.ua/) developed by the [**Ministry of Digital Transformation of Ukraine**](https://thedigital.gov.ua/).
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@diia-inhouse/types | AI (phantom-deps): Same-org dependency; declared phantom-dep is a stable false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 2.57.15 | 6 / 12 | |
| 2.57.14 | 6 / 12 | |
| 2.57.13 | 6 / 12 | |
| 2.57.12 | 6 / 12 | |
| 2.57.11 | 6 / 12 | |
| 2.57.10 | 6 / 12 | |
| 2.57.9 | 6 / 12 | |
| 2.57.8 | 6 / 12 | |
| 2.57.7 | 6 / 12 | |
| 2.57.6 | 6 / 12 | |
| 2.57.5 | 6 / 12 | |
| 2.57.4 | 6 / 12 | |
| 2.57.3 | 6 / 12 | |
| 2.57.2 | 6 / 12 | |
| 2.57.1 | 6 / 12 | |
| 2.57.0 | 6 / 12 | |
| 2.56.0 | 6 / 12 | |
| 2.55.1 | 6 / 12 | |
| 2.54.1 | 6 / 12 | |
| 2.54.0 | 6 / 12 | |
| 2.53.13 | 6 / 12 | |
| 2.53.12 | 6 / 12 | |
| 2.53.11 | 6 / 12 | |
| 2.53.10 | 6 / 12 | |
| 2.53.9 | 6 / 12 | |
| 2.53.8 | 6 / 12 | |
| 2.53.7 | 6 / 12 | |
| 2.53.6 | 6 / 12 | |
| 2.53.5 | 6 / 12 | |
| 2.53.4 | 6 / 12 | |
| 2.53.3 | 6 / 12 | |
| 2.53.2 | 6 / 12 | |
| 2.53.1 | 6 / 12 | |
| 2.53.0 | 6 / 12 | |
| 2.52.4 | 6 / 12 | |
| 2.52.3 | 6 / 12 | |
| 2.52.2 | 6 / 12 | |
| 2.52.0 | 6 / 12 | |
| 2.24.0 | 6 / 14 | |
| 2.23.0 | 6 / 14 | |
| 2.22.0 | 6 / 14 | |
| 2.19.1 | 6 / 14 | |
| 2.17.0 | 6 / 14 |
v2.57.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.