@mseva/digit-ui-module-ptr MIT 43 versions

@mseva/digit-ui-module-ptr

npm

43

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
npm-metadata	no-description	AI (npm-metadata): Consistent across the @mseva/digit-ui-* module family; not indicative of malice.	ai	2026/05/04
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom is a peer/bundled dep common in UI module packages; phantom-dep heuristic is a false positive here.	ai	2026/04/29
phantom-deps	phantom-dep:redux-thunk	AI (phantom-deps): redux-thunk used via config/middleware wiring, not direct import; stable false positive for this package.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Large org-internal module suite; missing metadata is a style issue, not a spam/malware indicator given 255 versions and 421-day history.	ai	2026/04/29
phantom-deps	phantom-dep:microbundle-crl	AI (phantom-deps): Build tool referenced in scripts, not imported; expected pattern.	ai	2026/04/29
phantom-deps	phantom-dep:@mseva/digit-ui-libraries	AI (phantom-deps): Same-org dep used indirectly via re-exports; stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:lodash.merge	AI (phantom-deps): Utility likely used indirectly; stable false positive for this package.	ai	2026/04/29

Versions (showing 43 of 43)

Version	Deps	Published
1.3.8	13 / 0	2026-04-29
1.2.9	13 / 0	2026-01-29
1.2.6	13 / 0	2026-01-20
1.2.5	13 / 0	2026-01-19
1.2.1	13 / 0	2026-01-12
1.1.85	13 / 0	2025-12-12
1.1.83	13 / 0	2025-12-11
1.1.82	13 / 0	2025-12-11
1.1.79	13 / 0	2025-12-10
1.1.78	13 / 0	2025-12-06
1.1.67	13 / 0	2025-11-30
1.1.65	13 / 0	2025-11-27
1.1.62	13 / 0	2025-11-24
1.1.55	13 / 0	2025-11-14
1.1.53	13 / 0	2025-11-13
1.1.52	13 / 0	2025-11-12
1.1.49	13 / 0	2025-11-10
1.1.47	13 / 0	2025-11-07
1.1.46	13 / 0	2025-11-07
1.1.45	13 / 0	2025-11-07
1.1.43	13 / 0	2025-11-06
1.1.41	13 / 0	2025-11-04
1.1.39	13 / 0	2025-11-03
1.1.38	13 / 0	2025-11-03
1.1.37	13 / 0	2025-10-31
1.1.36	13 / 0	2025-10-30
1.1.18	13 / 0	2025-10-14
1.0.91	13 / 0	2025-09-28
1.0.90	13 / 0	2025-09-26
1.0.82	13 / 0	2025-09-22
1.0.78	13 / 0	2025-09-16
1.0.65	13 / 0	2025-08-28
1.0.60	13 / 0	2025-08-21
1.0.58	13 / 0	2025-08-18
1.0.41	13 / 0	2025-07-21
1.0.39	13 / 0	2025-07-15
1.0.37	13 / 0	2025-06-24
1.0.36	13 / 0	2025-06-18
1.0.29	13 / 0	2025-05-29
1.0.27	13 / 0	2025-05-28
1.0.24	13 / 0	2025-05-22
1.0.15	13 / 0	2025-05-15
1.0.11	13 / 0	2025-05-13

v1.2.9

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.1.85

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.82

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.67

1 finding

LOW No provenance attestation provenance

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

v1.1.65

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.46

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.41

1 finding

LOW No provenance attestation provenance

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

v1.1.39

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. Consider requesting the maintainer enable provenance via CI/CD.

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

1 finding

LOW No provenance attestation provenance

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

v1.0.91

1 finding

LOW No provenance attestation provenance

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

v1.0.90

1 finding

LOW No provenance attestation provenance

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

v1.0.82

1 finding

LOW No provenance attestation provenance

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

v1.0.78

1 finding

LOW No provenance attestation provenance

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

v1.0.65

1 finding

LOW No provenance attestation provenance

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

v1.0.60

1 finding

LOW No provenance attestation provenance

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

v1.0.58

1 finding

LOW No provenance attestation provenance

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

v1.0.41

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.24

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

1 finding

LOW No provenance attestation provenance

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

v1.0.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.