← Home

@mseva/digit-ui-module-core

npm

Digit App Core Module contains all core components

50
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

anou1234anujsingh32mdmujibalamnarinderkumar1aashishgkpmg4nayandhawanmujibalam2000saurabhsingh0001

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/index.modern.js AI (source-diff): Standard microbundle ESM output; long lines are minified but imports are transparent and benign. ai
source-diff net-exec-file:dist/index.modern.js AI (source-diff): Bundle is a standard React/Redux UI module; no actual dropper pattern, just bundled imports from known packages. ai
source-diff source-size-tripled AI (source-diff): Size increase explained by addition of modern JS build output and source maps, not injected payload. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): Declared dependency; used as React peer in runtime context. ai
phantom-deps phantom-dep:redux-persist AI (phantom-deps): Declared dependency; referenced in config files as expected. ai
phantom-deps phantom-dep:microbundle-crl AI (phantom-deps): Declared dependency; used in build scripts as documented. ai

Versions (showing 50 of 50)

Version Deps Published
1.0.79 13 / 0
1.0.78 13 / 0
1.0.77 13 / 0
1.0.75 13 / 0
1.0.71 13 / 0
1.0.70 13 / 0
1.0.69 13 / 0
1.0.67 13 / 0
1.0.66 13 / 0
1.0.65 13 / 0
1.0.64 13 / 0
1.0.63 13 / 0
1.0.62 12 / 0
1.0.61 12 / 0
1.0.60 12 / 0
1.0.59 12 / 0
1.0.58 12 / 0
1.0.57 12 / 0
1.0.56 12 / 0
1.0.55 12 / 0
1.0.54 12 / 0
1.0.53 12 / 0
1.0.52 12 / 0
1.0.51 12 / 0
1.0.50 12 / 0
1.0.49 12 / 0
1.0.38 12 / 0
1.0.37 12 / 0
1.0.35 12 / 0
1.0.33 12 / 0
1.0.28 12 / 0
1.0.26 12 / 0
1.0.25 12 / 0
1.0.24 12 / 0
1.0.22 12 / 0
1.0.21 12 / 0
1.0.17 12 / 0
1.0.14 12 / 0
1.0.11 12 / 0
1.0.10 12 / 0
1.0.9 12 / 0
1.0.8 12 / 0
1.0.7 12 / 0
1.0.6 12 / 0
1.0.5 12 / 0
1.0.4 12 / 0
1.0.3 12 / 0
1.0.2 12 / 0
1.0.1 12 / 0
1.0.0 12 / 0

v1.0.70

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: anujsingh32 → nayandhawan (on 2026-03-13, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anujsingh32) on 2026-03-13, 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.65

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: aashishgkpmg4 → nayandhawan (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2026-01-13, 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.63

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 → anujsingh32 (on 2026-01-05, known maintainer) provenance

This version was published by a different npm account (anujsingh32) than the most recent previously approved version (nayandhawan) on 2026-01-05, but anujsingh32 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.62

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: aashishgkpmg4 → nayandhawan (on 2025-12-15, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2025-12-15, 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.57

1 finding
LOW No provenance attestation provenance

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

v1.0.56

1 finding
LOW No provenance attestation provenance

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

v1.0.55

1 finding
LOW No provenance attestation provenance

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

v1.0.54

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: anujsingh32 → nayandhawan (on 2025-12-02, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anujsingh32) on 2025-12-02, 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.4

2 findings
HIGH Publisher changed: anujsingh32 → nayandhawan (on 2025-03-31) provenance

This version was published by a different npm account than previous versions on 2025-03-31. 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.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

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.