@digitaldefiance/express-suite-react-components
React MUI components for Digital Defiance Express Suite
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:src/components/UserSettingsForm.js | AI (source-diff): Long lines are tsc-compiled JSX output with readable imports; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:src/components/FakeEmailAdminPanel.js | AI (source-diff): Long lines are TypeScript-compiled output, not obfuscation; content is readable React/MUI component code. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): MUI peer dependency; commonly declared but not directly imported in component libraries. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI peer dependency; commonly declared but not directly imported in component libraries. | ai | |
| phantom-deps | phantom-dep:@mui/x-date-pickers | AI (phantom-deps): MUI date picker dependency; may be re-exported or used indirectly in component library. | ai | |
| phantom-deps | phantom-dep:currency-codes | AI (phantom-deps): Utility dep likely used in config/type files; stable false positive for this package. | ai |
Versions (showing 51 of 176)
| Version | Deps | Published |
|---|---|---|
| 4.30.1 | 16 / 14 | |
| 4.30.0 | 16 / 14 | |
| 4.29.1 | 16 / 14 | |
| 4.29.0 | 16 / 14 | |
| 4.28.3 | 16 / 14 | |
| 4.28.2 | 16 / 14 | |
| 4.28.1 | 16 / 14 | |
| 4.28.0 | 16 / 14 | |
| 4.27.12 | 15 / 14 | |
| 4.27.11 | 15 / 14 | |
| 4.27.10 | 15 / 14 | |
| 4.27.9 | 15 / 14 | |
| 4.27.8 | 15 / 14 | |
| 4.27.7 | 15 / 14 | |
| 4.27.6 | 15 / 14 | |
| 4.27.5 | 15 / 14 | |
| 4.27.4 | 15 / 14 | |
| 4.27.3 | 15 / 14 | |
| 4.27.2 | 15 / 14 | |
| 4.27.1 | 15 / 14 | |
| 4.27.0 | 15 / 14 | |
| 4.26.26 | 14 / 14 | |
| 4.26.25 | 14 / 14 | |
| 4.26.24 | 14 / 14 | |
| 4.26.23 | 14 / 14 | |
| 4.26.22 | 14 / 14 | |
| 4.26.21 | 14 / 14 | |
| 4.26.20 | 14 / 14 | |
| 4.26.19 | 14 / 14 | |
| 4.26.18 | 14 / 14 | |
| 4.26.17 | 14 / 14 | |
| 4.26.16 | 14 / 14 | |
| 4.26.15 | 14 / 14 | |
| 4.26.14 | 14 / 14 | |
| 4.26.13 | 14 / 14 | |
| 4.26.12 | 14 / 14 | |
| 4.26.11 | 14 / 14 | |
| 4.26.10 | 14 / 14 | |
| 4.26.9 | 14 / 14 | |
| 4.26.8 | 14 / 14 | |
| 4.26.7 | 14 / 14 | |
| 4.26.6 | 14 / 14 | |
| 4.26.5 | 14 / 14 | |
| 4.26.4 | 14 / 14 | |
| 4.26.3 | 14 / 14 | |
| 4.26.2 | 14 / 14 | |
| 4.26.1 | 14 / 14 | |
| 4.26.0 | 14 / 14 | |
| 4.25.2 | 14 / 14 | |
| 4.25.1 | 14 / 14 | |
| 4.25.0 | 14 / 14 |
v4.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.