@mseva/digit-ui-module-common MIT 51 versions

@mseva/digit-ui-module-common

npm

Digit Common Payment Module

51

Versions

MIT

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

anou1234anujsingh32mdmujibalamnarinderkumar1aashishgkpmg4nayandhawanmujibalam2000saurabhsingh0001

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:redux	AI (phantom-deps): UI module declares redux as a runtime dep; phantom-dep heuristic fires on config-only references, stable FP for this package.	ai	2026/05/04
phantom-deps	phantom-dep:rooks	AI (phantom-deps): Same pattern — declared dep referenced in config, not a real phantom dep risk.	ai	2026/05/04
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom is a standard React runtime dep; phantom-dep heuristic is a stable FP here.	ai	2026/05/04
phantom-deps	phantom-dep:react-redux	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic is a stable FP for this UI module.	ai	2026/05/04
phantom-deps	phantom-dep:react-table	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic is a stable FP for this UI module.	ai	2026/05/04
phantom-deps	phantom-dep:redux-thunk	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic is a stable FP for this UI module.	ai	2026/05/04
phantom-deps	phantom-dep:microbundle-crl	AI (phantom-deps): Build tool declared in dependencies (not devDependencies); phantom-dep heuristic is a stable FP.	ai	2026/05/04

Versions (showing 51 of 154)

View all versions

Version	Deps	Published
1.1.91	15 / 0	2026-03-14
1.1.88	15 / 0	2026-02-10
1.1.87	15 / 0	2026-02-09
1.1.86	15 / 0	2026-02-06
1.1.85	15 / 0	2026-02-02
1.1.84	15 / 0	2026-02-02
1.1.83	15 / 0	2026-01-29
1.1.80	15 / 0	2026-01-19
1.1.79	15 / 0	2026-01-16
1.1.78	15 / 0	2026-01-15
1.1.77	15 / 0	2026-01-13
1.1.75	15 / 0	2026-01-09
1.1.72	15 / 0	2026-01-05
1.1.71	15 / 0	2026-01-02
1.1.70	15 / 0	2026-01-02
1.1.68	15 / 0	2025-12-24
1.1.66	15 / 0	2025-12-17
1.1.64	15 / 0	2025-12-16
1.1.61	15 / 0	2025-12-12
1.1.59	15 / 0	2025-12-11
1.1.58	15 / 0	2025-12-10
1.1.57	15 / 0	2025-12-10
1.1.56	15 / 0	2025-12-10
1.1.55	15 / 0	2025-12-06
1.1.53	15 / 0	2025-12-04
1.1.52	15 / 0	2025-12-03
1.1.51	15 / 0	2025-12-03
1.1.48	15 / 0	2025-12-02
1.1.47	15 / 0	2025-12-02
1.1.45	15 / 0	2025-12-01
1.1.43	15 / 0	2025-11-28
1.1.42	15 / 0	2025-11-28
1.1.40	15 / 0	2025-11-27
1.1.38	15 / 0	2025-11-26
1.1.37	15 / 0	2025-11-25
1.1.34	15 / 0	2025-11-20
1.1.32	15 / 0	2025-11-18
1.1.31	15 / 0	2025-11-18
1.1.30	15 / 0	2025-11-17
1.1.29	15 / 0	2025-11-16
1.1.26	15 / 0	2025-11-14
1.1.24	15 / 0	2025-11-13
1.1.21	15 / 0	2025-11-11
1.1.19	15 / 0	2025-11-10
1.1.18	15 / 0	2025-11-09
1.1.17	15 / 0	2025-11-07
1.1.16	15 / 0	2025-11-06
1.1.15	15 / 0	2025-11-06
1.1.12	15 / 0	2025-11-03
1.1.11	15 / 0	2025-10-31
1.1.10	15 / 0	2025-10-30

v1.1.91

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.1.88

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.1.87

1 finding

LOW No provenance attestation provenance

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

v1.1.86

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.1.85

1 finding

LOW No provenance attestation provenance

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

v1.1.84

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.1.83

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.1.80

1 finding

LOW No provenance attestation provenance

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

v1.1.79

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.1.78

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.1.77

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.1.75

1 finding

LOW No provenance attestation provenance

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

v1.1.72

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.1.71

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.1.70

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.1.68

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.1.66

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.1.64

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.1.61

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.1.59

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.1.58

1 finding

LOW No provenance attestation provenance

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

v1.1.57

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.1.56

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.1.55

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.1.53

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.1.52

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.1.51

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.1.48

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.1.47

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.1.45

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.1.43

1 finding

LOW No provenance attestation provenance

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

v1.1.42

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.1.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.

v1.1.38

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.1.37

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.1.34

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.1.32

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.1.31

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.1.30

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.1.29

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.1.26

1 finding

LOW No provenance attestation provenance

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

v1.1.24

1 finding

LOW No provenance attestation provenance

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

v1.1.21

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.1.19

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.1.18

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.1.17

1 finding

LOW No provenance attestation provenance

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

v1.1.16

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.1.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.1.12

1 finding

LOW No provenance attestation provenance

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

v1.1.11

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.1.10

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.