@chipstcp/digit-ui-module-common
Digit Common Payment 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:rooks | AI (phantom-deps): Same bundled UI module pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Same bundled UI module pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Same bundled UI module pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:redux | AI (phantom-deps): UI module declares deps for peer/bundler resolution; phantom-dep false positive pattern for this package. | ai | |
| phantom-deps | phantom-dep:redux-thunk | AI (phantom-deps): Same bundled UI module pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): Build tool declared as dep but used only in scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-table | AI (phantom-deps): Same bundled UI module pattern; stable false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 15 / 0 | |
| 1.0.8 | 15 / 0 | |
| 1.0.7 | 15 / 0 | |
| 1.0.6 | 15 / 0 | |
| 1.0.5 | 15 / 0 | |
| 1.0.4 | 15 / 0 | |
| 1.0.3 | 15 / 0 | |
| 1.0.1 | 15 / 0 | |
| 1.0.0 | 15 / 0 |
v1.0.8
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 finding[Accepted risk] 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.
v1.0.3
1 finding[Accepted risk] 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.