@f5xc-salesdemos/docs-theme
F5 Distributed Cloud branded Starlight documentation 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package with clean history; provenance absence is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@f5xc-salesdemos/i18n-core | AI (dependencies): Same org namespace (@f5xc-salesdemos); consistent with other deps in this package family. | ai | |
| dependencies | unvetted-dep:starlight-openapi | AI (dependencies): starlight-openapi is a legitimate Starlight plugin; consistent with this docs-theme package's purpose. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 15 / 2 | |
| 3.5.10 | 15 / 2 | |
| 3.5.9 | 15 / 2 | |
| 3.5.8 | 15 / 2 | |
| 3.5.7 | 15 / 2 | |
| 3.5.4 | 14 / 1 | |
| 3.5.3 | 14 / 1 | |
| 3.5.2 | 14 / 1 | |
| 3.5.1 | 14 / 1 | |
| 3.5.0 | 14 / 1 | |
| 3.4.2 | 14 / 1 | |
| 3.4.1 | 14 / 1 | |
| 3.4.0 | 14 / 1 | |
| 3.3.2 | 14 / 1 | |
| 3.3.1 | 14 / 1 | |
| 3.3.0 | 14 / 1 | |
| 3.1.0 | 14 / 1 | |
| 3.0.3 | 14 / 1 | |
| 3.0.2 | 14 / 1 | |
| 3.0.1 | 14 / 1 | |
| 3.0.0 | 14 / 1 | |
| 2.27.1 | 13 / 1 | |
| 2.27.0 | 13 / 1 | |
| 2.26.0 | 13 / 1 | |
| 2.25.0 | 13 / 1 | |
| 2.24.5 | 12 / 1 | |
| 2.24.4 | 12 / 1 | |
| 2.24.3 | 12 / 1 | |
| 2.24.2 | 12 / 1 | |
| 2.24.1 | 12 / 1 | |
| 2.24.0 | 12 / 1 | |
| 2.23.0 | 11 / 1 | |
| 2.22.4 | 11 / 1 | |
| 2.19.1 | 11 / 1 | |
| 2.19.0 | 11 / 1 | |
| 2.16.2 | 10 / 1 | |
| 2.16.0 | 10 / 1 | |
| 2.10.2 | 10 / 1 | |
| 2.7.1 | 10 / 1 | |
| 2.2.5 | 10 / 1 | |
| 2.0.3 | 10 / 1 |
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.