@egovernments/digit-ui-module-cms
PGR Module UI
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@egovernments/digit-ui-module-hrms | AI (phantom-deps): Same-org dep declared for bundling/config use; not a malicious phantom dependency pattern. | ai | |
| phantom-deps | phantom-dep:@egovernments/digit-ui-module-core | AI (phantom-deps): Same-org dep likely used transitively; phantom-dep heuristic is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@egovernments/digit-ui-components | AI (dependencies): Same-org DIGIT UI ecosystem dependency; consistent across versions. | ai | |
| dependencies | unvetted-dep:@egovernments/digit-ui-react-components | AI (dependencies): Same-org DIGIT UI ecosystem dependency; consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): egovernments org packages consistently lack Sigstore attestation; not a malice indicator for this ecosystem. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom declared as dep but used transitively; common pattern in UI module bundles. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Declared dep used indirectly via component library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-date-range | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.0.45 | 13 / 1 | |
| 1.0.44 | 13 / 1 | |
| 1.0.43 | 13 / 1 | |
| 1.0.42 | 13 / 1 | |
| 1.0.41 | 13 / 1 | |
| 1.0.40 | 13 / 1 | |
| 1.0.39 | 13 / 1 | |
| 1.0.38 | 13 / 1 | |
| 1.0.37 | 13 / 1 | |
| 1.0.36 | 13 / 1 | |
| 1.0.35 | 13 / 1 | |
| 1.0.33 | 13 / 1 | |
| 1.0.32 | 13 / 1 | |
| 1.0.31 | 13 / 1 | |
| 1.0.30 | 13 / 1 | |
| 1.0.29 | 12 / 1 | |
| 1.0.28 | 12 / 1 | |
| 1.0.27 | 12 / 1 | |
| 1.0.26 | 12 / 1 | |
| 1.0.25 | 12 / 1 | |
| 1.0.24 | 12 / 1 | |
| 1.0.23 | 12 / 1 | |
| 1.0.22 | 12 / 1 | |
| 1.0.21 | 12 / 1 | |
| 1.0.20 | 12 / 1 | |
| 1.0.19 | 12 / 1 | |
| 1.0.18 | 13 / 1 | |
| 1.0.17 | 12 / 1 | |
| 1.0.16 | 12 / 1 | |
| 1.0.15 | 12 / 1 | |
| 1.0.14 | 12 / 1 | |
| 1.0.13 | 12 / 1 | |
| 1.0.12 | 12 / 1 | |
| 1.0.11 | 12 / 1 | |
| 1.0.10 | 12 / 1 | |
| 1.0.9 | 12 / 1 | |
| 1.0.8 | 12 / 1 | |
| 1.0.7 | 12 / 1 | |
| 1.0.6 | 12 / 1 | |
| 1.0.3 | 12 / 1 | |
| 1.0.2 | 12 / 1 | |
| 1.0.1 | 12 / 1 | |
| 1.0.0 | 12 / 1 | |
| 0.0.1 | 12 / 0 |
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.