@mseva/digit-ui-module-core
Digit App Core Module contains all core components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.0.77 | 13 / 0 | |
| 1.0.75 | 13 / 0 | |
| 1.0.71 | 13 / 0 | |
| 1.0.69 | 13 / 0 | |
| 1.0.67 | 13 / 0 | |
| 1.0.66 | 13 / 0 | |
| 1.0.64 | 13 / 0 | |
| 1.0.61 | 12 / 0 | |
| 1.0.60 | 12 / 0 | |
| 1.0.59 | 12 / 0 | |
| 1.0.58 | 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 |
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anujsingh32) on 2026-05-19, 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.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.