@chipstcp/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Sourcemaps/unminified bundle added, consistent with build config, not injected payload. | ai | |
| source-diff | net-exec-file:dist/index.modern.js | AI (source-diff): Bundled React app code (microbundle output), not a dropper/loader. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared dependency; used as React peer library in this UI module. | ai | |
| phantom-deps | phantom-dep:redux-persist | AI (phantom-deps): Declared dependency; referenced in config files as documented. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Declared dependency; used in build scripts (start/build commands). | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 12 / 0 | |
| 1.0.6 | 12 / 0 | |
| 1.0.5 | 12 / 0 | |
| 1.0.3 | 12 / 0 | |
| 1.0.2 | 12 / 0 | |
| 1.0.1 | 12 / 0 | |
| 1.0.0 | 13 / 0 |
v1.0.3
3 findings[Reject — re-review on republish] (prior reject: AI (provenance): Publisher changed to an unknown account with no track record; generalizes until original maintainer is restored.) This version was published by a different npm account than previous versions on 2026-03-22. This could indicate a legitimate maintainer transition or an account compromise.
[Reject — re-review on republish] (prior reject: AI (source-diff): New large file with net+exec pattern added alongside suspicious publisher change; high-risk combination.) 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.0.2
3 findings[Reject — re-review on republish] (prior reject: AI (provenance): Publisher changed to an unknown account with no track record; generalizes until original maintainer is restored.) This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
[Reject — re-review on republish] (prior reject: AI (source-diff): New large file with net+exec pattern added alongside suspicious publisher change; high-risk combination.) 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.