@mseva/digit-ui-module-engagement
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): File is a standard microbundle-crl output with readable named imports; long lines are minified bundle, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index.modern.js | AI (source-diff): Network calls and dynamic code are from React/Redux/react-query patterns in a UI module bundle, not dropper behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal government/civic-tech UI module; sparse metadata is consistent with org-internal publishing practices across 44 versions. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a standard peer/build dep in React module packages; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:redux-thunk | AI (phantom-deps): redux-thunk used as runtime dep via redux middleware config, not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): microbundle-crl is a build tool referenced in scripts, not imported in source; phantom-dep false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.34 | 13 / 0 | |
| 1.1.33 | 13 / 0 | |
| 1.1.32 | 13 / 0 | |
| 1.1.31 | 13 / 0 | |
| 1.1.18 | 13 / 0 | |
| 1.1.15 | 13 / 0 | |
| 1.1.14 | 13 / 0 |
v1.1.34
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.