@djb25/digit-ui-react-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): Sample shows readable compiled React/JSX code; long lines are from bundled component library, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index.modern.js | AI (source-diff): Network calls are from @googlemaps/js-api-loader; dynamic execution is standard React rendering. No dropper pattern present. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of source maps (1.9MB each) and modern ES module build output. | ai |
v1.0.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: djb25.
Newly 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.