@redocly/theme
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Redocly internal shared UI lib; sparse README and no public repo URL are expected for a private/internal package. | ai | |
| source-diff | obfuscated-file:lib/icons/MoleculesIcon/MoleculesIcon.js | AI (source-diff): File is standard tsc-compiled output with readable SVG path data; long lines from inline SVG coordinates, not obfuscation. | ai | |
| phantom-deps | phantom-dep:react-calendar | AI (phantom-deps): react-calendar is listed as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.65.0 | 16 / 29 | |
| 0.64.0 | 16 / 29 | |
| 0.62.1 | 16 / 29 | |
| 0.62.0 | 16 / 29 | |
| 0.61.1 | 16 / 29 | |
| 0.61.0 | 16 / 29 | |
| 0.60.1 | 16 / 29 | |
| 0.60.0 | 16 / 29 | |
| 0.59.0 | 17 / 34 | |
| 0.58.1 | 17 / 34 | |
| 0.58.0 | 17 / 34 | |
| 0.57.1 | 16 / 34 | |
| 0.57.0 | 16 / 34 | |
| 0.56.3 | 15 / 38 | |
| 0.56.2 | 15 / 38 | |
| 0.56.1 | 15 / 38 | |
| 0.56.0 | 15 / 38 | |
| 0.55.0 | 15 / 38 | |
| 0.54.3 | 14 / 38 | |
| 0.54.2 | 14 / 38 | |
| 0.54.1 | 14 / 38 | |
| 0.54.0 | 14 / 38 | |
| 0.53.0 | 13 / 38 |
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.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.56.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.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.