@salutejs/sdds-dfa
Salute Design System / React UI kit for SDDS DFA web applications
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:dist/styled-components/cjs/components/TextFieldSlider/TextFieldSlider.clear.config.js | AI (source-diff): SWC-compiled CJS output with long lines from template literal arrays; standard build artifact for this design system package. | ai | |
| source-diff | obfuscated-file:dist/styled-components/cjs/components/TextFieldSlider/TextFieldSlider.config.js | AI (source-diff): SWC-compiled CJS output with long lines from template literal arrays; standard build artifact for this design system package. | ai | |
| provenance | no-provenance | AI (provenance): Large org UI kit; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.349.1 | 2 / 24 | |
| 0.349.0 | 2 / 24 | |
| 0.347.0 | 2 / 25 | |
| 0.346.0 | 2 / 25 | |
| 0.345.0 | 2 / 25 | |
| 0.344.0 | 2 / 25 | |
| 0.343.0 | 2 / 25 | |
| 0.342.0 | 2 / 25 | |
| 0.341.0 | 2 / 25 | |
| 0.340.0 | 2 / 25 | |
| 0.339.0 | 2 / 25 | |
| 0.338.0 | 2 / 25 | |
| 0.333.0 | 2 / 25 | |
| 0.332.0 | 2 / 25 | |
| 0.331.0 | 2 / 25 | |
| 0.330.0 | 2 / 25 | |
| 0.312.0 | 2 / 34 | |
| 0.311.0 | 2 / 34 | |
| 0.309.1 | 2 / 34 | |
| 0.309.0 | 2 / 34 | |
| 0.308.0 | 2 / 34 |
v0.349.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.349.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.347.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.342.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.341.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.340.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.339.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.338.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.333.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.332.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.
v0.331.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.
v0.330.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.
v0.312.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.311.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.
v0.309.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.309.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.
v0.308.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.