@mseva/digit-ui-module-noc MIT 44 versions

@mseva/digit-ui-module-noc

npm

44

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
bogus-package	bogus-package	AI (bogus-package): Internal enterprise UI module; missing metadata is a hygiene issue, not a malice indicator across 133 versions.	ai	2026/05/19
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom is a peer/build-time dep; phantom-dep heuristic false positive for this package.	ai	2026/05/19
phantom-deps	phantom-dep:redux-thunk	AI (phantom-deps): Stable false positive; redux-thunk used transitively in this UI module.	ai	2026/05/19
phantom-deps	phantom-dep:lodash.merge	AI (phantom-deps): Stable false positive; lodash.merge used in config/build context.	ai	2026/05/19
phantom-deps	phantom-dep:microbundle-crl	AI (phantom-deps): microbundle-crl is a build tool referenced in scripts; phantom-dep heuristic false positive.	ai	2026/05/19

Versions (showing 44 of 44)

Version	Deps	Published
1.0.88	14 / 0	2026-06-04
1.0.87	14 / 0	2026-06-01
1.0.86	14 / 0	2026-05-20
1.0.85	14 / 0	2026-05-07
1.0.84	13 / 0	2026-05-07
1.0.83	13 / 0	2026-04-17
1.0.82	13 / 0	2026-04-12
1.0.81	13 / 0	2026-04-01
1.0.69	13 / 0	2026-02-03
1.0.68	13 / 0	2026-02-03
1.0.66	13 / 0	2026-02-02
1.0.65	13 / 0	2026-02-02
1.0.59	13 / 0	2026-01-22
1.0.55	13 / 0	2026-01-21
1.0.54	13 / 0	2026-01-21
1.0.53	13 / 0	2026-01-21
1.0.52	13 / 0	2026-01-19
1.0.47	13 / 0	2026-01-15
1.0.46	13 / 0	2026-01-14
1.0.41	13 / 0	2026-01-11
1.0.35	13 / 0	2026-01-01
1.0.32	13 / 0	2025-12-12
1.0.28	13 / 0	2025-12-01
1.0.27	13 / 0	2025-11-25
1.0.26	13 / 0	2025-11-10
1.0.22	13 / 0	2025-10-14
1.0.21	13 / 0	2025-10-14
1.0.20	13 / 0	2025-10-09
1.0.19	13 / 0	2025-10-09
1.0.18	13 / 0	2025-10-07
1.0.17	13 / 0	2025-10-03
1.0.16	13 / 0	2025-10-03
1.0.15	13 / 0	2025-09-28
1.0.14	13 / 0	2025-09-26
1.0.13	13 / 0	2025-09-23
1.0.12	13 / 0	2025-09-22
1.0.11	13 / 0	2025-09-20
1.0.10	13 / 0	2025-09-16
1.0.9	13 / 0	2025-09-09
1.0.8	13 / 0	2025-08-28
1.0.7	13 / 0	2025-08-25
1.0.6	8 / 0	2025-08-21
1.0.4	13 / 0	2025-08-18
1.0.3	8 / 0	2025-05-22

v1.0.88

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → nayandhawan (on 2026-06-04, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anou1234) on 2026-06-04, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.87

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: nayandhawan → anou1234 (on 2026-06-01, known maintainer) provenance

This version was published by a different npm account (anou1234) than the most recent previously approved version (nayandhawan) on 2026-06-01, but anou1234 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.86

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.