@reltio/design
Reltio Design Platform
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@storybook/mcp | AI (phantom-deps): Config-only reference; consistent with storybook tooling in a design system package. | ai | |
| phantom-deps | phantom-dep:rc-tree | AI (phantom-deps): Established tree component; phantom finding likely due to indirect import pattern. | ai | |
| phantom-deps | phantom-dep:@ui5/webcomponents | AI (phantom-deps): UI5 webcomponents referenced in config files (e.g. bundler/loader config); not a direct import pattern is expected. | ai | |
| phantom-deps | phantom-dep:@ui5/webcomponents-fiori | AI (phantom-deps): Same as @ui5/webcomponents — config-file reference pattern for UI5 components is stable for this package. | ai | |
| source-diff | obfuscated-file:icons/Applications.js | AI (source-diff): Long lines are inline SVG path data in React icon components, not obfuscation. Stable pattern for this icon library package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Design system icon library; large number of new files is expected as icon set grows. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects addition of icon library files, not injected payloads. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private org design library; missing repo/homepage is common for internal packages at early versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 10 / 2 | |
| 1.1.0 | 10 / 2 | |
| 1.0.2 | 10 / 2 | |
| 1.0.1 | 12 / 2 | |
| 1.0.0 | 12 / 2 | |
| 0.6.0 | 7 / 2 | |
| 0.5.0 | 7 / 2 | |
| 0.4.0 | 4 / 2 | |
| 0.3.3 | 4 / 2 | |
| 0.3.2 | 4 / 2 | |
| 0.3.1 | 4 / 2 | |
| 0.3.0 | 3 / 2 | |
| 0.2.1 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.1 | 3 / 7 | |
| 0.1.0 | 3 / 7 | |
| 0.0.3 | 2 / 7 | |
| 0.0.2 | 2 / 7 | |
| 0.0.1 | 1 / 7 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.