@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/core/types/l10n.d.ts | AI (source-diff): Long line is a generated TS union type for i18n keys, not minified/obfuscated code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): file-saver and jszip are well-known libs matching new export features. | ai | |
| source-diff | obfuscated-file:lib/icons/DocumentGraphqlIcon/DocumentGraphqlIcon.js | AI (source-diff): Long lines are SVG path data in compiled TS, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/icons/DocumentJsonIcon/DocumentJsonIcon.js | AI (source-diff): Long lines are SVG path data in compiled TS, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/icons/DocumentReactIcon/DocumentReactIcon.js | AI (source-diff): Long lines are SVG path data in compiled TS, not obfuscation. | ai | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 0.67.0 | 16 / 29 | |
| 0.66.0 | 17 / 29 | |
| 0.65.0 | 16 / 29 | |
| 0.64.0 | 16 / 29 | |
| 0.63.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 | |
| 0.48.2 | 11 / 39 | |
| 0.48.0 | 11 / 39 | |
| 0.47.1 | 11 / 39 | |
| 0.47.0 | 9 / 35 | |
| 0.46.5 | 9 / 35 | |
| 0.46.4 | 9 / 35 | |
| 0.46.3 | 9 / 35 | |
| 0.46.2 | 9 / 35 | |
| 0.46.1 | 9 / 35 | |
| 0.46.0 | 9 / 35 | |
| 0.45.11 | 9 / 36 | |
| 0.45.10 | 9 / 36 | |
| 0.45.9 | 9 / 36 | |
| 0.45.8 | 9 / 36 | |
| 0.45.7 | 9 / 36 | |
| 0.45.6 | 9 / 36 | |
| 0.45.5 | 9 / 36 | |
| 0.45.4 | 9 / 36 | |
| 0.45.3 | 9 / 36 | |
| 0.45.2 | 9 / 36 | |
| 0.45.1 | 9 / 36 | |
| 0.45.0 | 9 / 36 | |
| 0.44.9 | 9 / 36 | |
| 0.44.8 | 9 / 36 | |
| 0.44.7 | 9 / 36 | |
| 0.44.6 | 9 / 36 | |
| 0.44.5 | 9 / 52 | |
| 0.44.4 | 9 / 54 | |
| 0.44.3 | 9 / 54 | |
| 0.44.2 | 9 / 54 | |
| 0.44.1 | 9 / 54 | |
| 0.42.1 | 9 / 54 | |
| 0.41.0 | 9 / 54 | |
| 0.40.6 | 9 / 54 | |
| 0.40.5 | 9 / 54 | |
| 0.40.4 | 9 / 54 | |
| 0.40.3 | 9 / 54 | |
| 0.40.2 | 9 / 54 | |
| 0.40.1 | 9 / 54 | |
| 0.40.0 | 9 / 54 | |
| 0.39.1 | 9 / 54 | |
| 0.39.0 | 9 / 54 | |
| 0.38.8 | 9 / 54 | |
| 0.38.7 | 9 / 54 | |
| 0.38.6 | 9 / 54 | |
| 0.38.5 | 9 / 54 | |
| 0.38.4 | 9 / 54 | |
| 0.38.3 | 9 / 54 | |
| 0.38.2 | 9 / 54 | |
| 0.38.1 | 9 / 54 | |
| 0.38.0 | 9 / 54 | |
| 0.37.7 | 9 / 54 | |
| 0.37.6 | 9 / 54 | |
| 0.37.4 | 9 / 54 | |
| 0.37.3 | 9 / 54 | |
| 0.37.2 | 9 / 54 | |
| 0.37.1 | 9 / 54 | |
| 0.37.0 | 9 / 54 | |
| 0.36.3 | 7 / 53 |
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
4 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.
Newly 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.48.0
4 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.
Newly 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.47.1
4 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.
Newly 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.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.11
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.45.10
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.45.9
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.45.8
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.45.7
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.45.6
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.45.5
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.45.4
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.45.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.45.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.45.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.45.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.44.9
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.44.8
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.44.7
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.44.6
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.44.5
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.44.4
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.44.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.44.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.44.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.42.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.41.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.40.6
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.40.5
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.40.4
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.40.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.40.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.40.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.40.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.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.