@egovernments/digit-ui-module-core No license 36 versions

@egovernments/digit-ui-module-core

npm

36

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jagankumar-egovsathishp-egovegovmanswathi-egov

Keywords

digitegovdpgdigit-uicore

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both publishers are within the @egovernments org; transition appears legitimate with no code changes.	ai	2026/05/23
provenance	no-provenance	AI (provenance): Established eGov package with 421 versions; lack of provenance is consistent across all versions and not a risk indicator here.	ai	2026/05/23
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom declared as peer/runtime dep in package.json; phantom-dep heuristic fires due to bundler pattern, not a real issue.	ai	2026/05/13
phantom-deps	phantom-dep:react-tooltip	AI (phantom-deps): react-tooltip declared as runtime dep; phantom-dep heuristic fires due to bundler pattern, not a real issue.	ai	2026/05/13

Versions (showing 36 of 36)

Version	Deps	Published
1.9.15	12 / 0	2026-03-18
1.9.14	12 / 0	2026-03-12
1.9.12	12 / 0	2026-02-17
1.9.11	12 / 0	2026-02-16
1.9.10	12 / 0	2026-01-13
1.9.9	12 / 0	2025-12-24
1.9.8	12 / 0	2025-12-12
1.9.7	12 / 0	2025-12-09
1.9.6	12 / 0	2025-11-26
1.9.5	12 / 0	2025-11-26
1.9.4	12 / 0	2025-11-25
1.9.3	12 / 0	2025-11-21
1.9.2	12 / 0	2025-11-12
1.9.1	12 / 0	2025-11-07
1.9.0	12 / 0	2025-10-28
1.8.55	12 / 0	2025-10-10
1.8.54	12 / 0	2025-10-09
1.8.53	12 / 0	2025-10-08
1.8.52	12 / 0	2025-10-07
1.8.51	12 / 0	2025-10-06
1.8.50	12 / 0	2025-10-03
1.8.49	12 / 0	2025-10-03
1.8.48	12 / 0	2025-10-03
1.8.47	12 / 0	2025-09-22
1.8.46	12 / 0	2025-09-15
1.8.45	12 / 0	2025-09-08
1.8.44	12 / 0	2025-07-15
1.8.43	12 / 0	2025-07-01
1.8.42	12 / 0	2025-06-18
1.8.41	12 / 0	2025-06-12
1.8.40	12 / 0	2025-06-12
1.8.39	12 / 0	2025-06-11
1.8.38	12 / 0	2025-06-10
1.8.37	12 / 0	2025-06-05
1.8.36	12 / 0	2025-05-27
1.7.40	10 / 0	2025-05-28

v1.9.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.9.14

2 findings

HIGH Publisher changed: jagankumar-egov → swathi-egov (on 2026-03-12) provenance

This version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.53

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.52

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.51

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.48

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.47

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.45

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.