@seqera/docusaurus-theme-seqera
Seqera docs theme for Docusaurus
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:infima | AI (dependencies): infima is Docusaurus's official CSS framework, standard theme dependency. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency. | ai | |
| phantom-deps | phantom-dep:@seqera/docusaurus-preset-seqera | AI (phantom-deps): Same-org sibling package, not a real concern. | ai | |
| source-diff | obfuscated-file:lib/theme/SearchPage/index.js | AI (source-diff): Legit swizzled Docusaurus component with long lines, not true obfuscation; matches search deps added. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Docusaurus internal dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@docusaurus/logger | AI (phantom-deps): Docusaurus internal dep; not directly imported by design. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard Docusaurus/Prism language loader pattern; stable across all versions of this theme. | ai | |
| phantom-deps | phantom-dep:@docusaurus/plugin-content-pages | AI (phantom-deps): Docusaurus plugin dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@docusaurus/module-type-aliases | AI (phantom-deps): Docusaurus type-only dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:infima | AI (phantom-deps): Docusaurus config-referenced dep; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:raw-loader | AI (phantom-deps): Webpack config-referenced dep; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): Docusaurus peer/config dep; not directly imported by design. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.0.38 | 30 / 8 | |
| 1.0.37 | 30 / 8 | |
| 1.0.36 | 30 / 8 | |
| 1.0.35 | 30 / 8 | |
| 1.0.34 | 30 / 8 | |
| 1.0.33 | 30 / 8 | |
| 1.0.32 | 30 / 8 | |
| 1.0.31 | 30 / 8 | |
| 1.0.30 | 30 / 8 | |
| 1.0.29 | 30 / 8 | |
| 1.0.27 | 30 / 8 | |
| 1.0.26 | 30 / 8 | |
| 1.0.25 | 28 / 8 | |
| 1.0.24 | 28 / 8 | |
| 1.0.22 | 28 / 8 | |
| 1.0.21 | 28 / 8 | |
| 1.0.20 | 28 / 8 | |
| 1.0.19 | 28 / 8 | |
| 1.0.18 | 28 / 8 | |
| 1.0.17 | 28 / 8 | |
| 1.0.16 | 28 / 8 | |
| 1.0.15 | 28 / 8 | |
| 1.0.13 | 28 / 8 | |
| 1.0.12 | 28 / 8 | |
| 1.0.11 | 28 / 8 | |
| 1.0.10 | 28 / 8 | |
| 1.0.9 | 28 / 8 | |
| 1.0.8 | 28 / 8 | |
| 1.0.7 | 28 / 8 | |
| 1.0.6 | 28 / 9 | |
| 1.0.4 | 28 / 9 | |
| 1.0.3 | 28 / 10 | |
| 1.0.2 | 29 / 9 | |
| 1.0.0 | 29 / 8 |
v1.0.37
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.
v1.0.36
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.
v1.0.35
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.
v1.0.34
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.
v1.0.33
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.
v1.0.32
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.
v1.0.31
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.
v1.0.30
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.
v1.0.29
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.
v1.0.27
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.
v1.0.26
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.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.