@djb25/digit-ui-module-bills
BILLS
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 output; network calls are app-level API wrappers, not malicious. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from adding dist bundle + source maps; expected for microbundle output. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React peer dependency; typical for UI modules built with microbundle. | ai | |
| phantom-deps | phantom-dep:react-query | AI (phantom-deps): Declared dependency used via config/scripts; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Build tool invoked in scripts; not imported in source code. | ai |
v1.0.2
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.