@mseva/digit-ui-module-mcollect
Digit Misc Collections Module
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 | net-exec-file:dist/index.modern.js | AI (source-diff): Bundle is a standard React UI module; no actual dropper/loader behavior in the code sample. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React-dom is a peer/build dependency; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Declared and used in build config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Build tool in scripts; phantom-dep fires on config references, not actual imports. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.15 | 9 / 0 | |
| 1.0.14 | 9 / 0 | |
| 1.0.13 | 9 / 0 | |
| 1.0.12 | 9 / 0 | |
| 1.0.11 | 9 / 0 | |
| 1.0.10 | 9 / 0 | |
| 1.0.9 | 9 / 0 | |
| 1.0.7 | 9 / 0 | |
| 1.0.6 | 9 / 0 | |
| 1.0.5 | 9 / 0 | |
| 1.0.4 | 9 / 0 |
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.