@djb25/digit-ui-module-wt
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): Bundled React UI module with leaflet + socket.io imports; not malware. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from bundling leaflet/socket.io/react-leaflet; expected. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:jspdf-autotable | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:jspdf | AI (phantom-deps): Listed as runtime dep in package.json; phantom-dep heuristic false positive for bundled module. | ai | |
| phantom-deps | phantom-dep:@djb25/digit-ui-libraries | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Build tool listed as dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for this bundled module. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.0.64 | 16 / 0 | |
| 1.0.63 | 16 / 0 | |
| 1.0.62 | 16 / 0 | |
| 1.0.61 | 16 / 0 | |
| 1.0.60 | 16 / 0 | |
| 1.0.59 | 16 / 0 | |
| 1.0.58 | 16 / 0 | |
| 1.0.57 | 16 / 0 | |
| 1.0.56 | 16 / 0 | |
| 1.0.55 | 16 / 0 | |
| 1.0.54 | 16 / 0 | |
| 1.0.53 | 16 / 0 | |
| 1.0.52 | 16 / 0 | |
| 1.0.51 | 16 / 0 | |
| 1.0.50 | 16 / 0 | |
| 1.0.49 | 16 / 0 | |
| 1.0.48 | 16 / 0 | |
| 1.0.47 | 16 / 0 | |
| 1.0.46 | 16 / 0 | |
| 1.0.45 | 16 / 0 | |
| 1.0.44 | 16 / 0 | |
| 1.0.43 | 16 / 0 | |
| 1.0.42 | 16 / 0 | |
| 1.0.41 | 16 / 0 | |
| 1.0.40 | 16 / 0 | |
| 1.0.39 | 16 / 0 | |
| 1.0.38 | 16 / 0 | |
| 1.0.37 | 16 / 0 | |
| 1.0.36 | 16 / 0 | |
| 1.0.35 | 16 / 0 | |
| 1.0.34 | 16 / 0 | |
| 1.0.33 | 16 / 0 | |
| 1.0.32 | 16 / 0 | |
| 1.0.31 | 16 / 0 | |
| 1.0.30 | 16 / 0 | |
| 1.0.29 | 16 / 0 | |
| 1.0.28 | 16 / 0 | |
| 1.0.27 | 16 / 0 | |
| 1.0.26 | 16 / 0 | |
| 1.0.25 | 16 / 0 | |
| 1.0.24 | 16 / 0 | |
| 1.0.23 | 16 / 0 | |
| 1.0.22 | 16 / 0 | |
| 1.0.3 | 12 / 0 | |
| 1.0.2 | 12 / 0 |
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.36
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.34
1 findingPackage 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.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
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.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage 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.23
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.