@red-hat-developer-hub/backstage-plugin-lightspeed-backend
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:llama-stack-client | AI (dependencies): llama-stack-client is a legitimate LLM client library appropriate for this AI assistant backend plugin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established RHDH plugin with 40 versions; bot publisher is a CI account, not an account takeover indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped Red Hat org package; missing description is a cosmetic issue, not a malice signal. | ai | |
| phantom-deps | phantom-dep:@langchain/core | AI (phantom-deps): LangChain deps used via config/type references in a Backstage plugin; not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:@langchain/openai | AI (phantom-deps): Same as @langchain/core — config-file reference pattern for this plugin. | ai | |
| phantom-deps | phantom-dep:llama-stack-client | AI (phantom-deps): Referenced in config files; stable false positive for this plugin's architecture. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.8.5 | 18 / 11 | |
| 2.8.4 | 18 / 11 | |
| 2.8.3 | 18 / 11 | |
| 2.8.2 | 18 / 11 | |
| 2.8.1 | 18 / 11 | |
| 2.8.0 | 18 / 11 | |
| 2.7.1 | 18 / 11 | |
| 2.7.0 | 18 / 11 | |
| 2.6.8 | 18 / 11 | |
| 2.6.7 | 18 / 11 | |
| 2.6.6 | 18 / 11 | |
| 2.6.5 | 18 / 11 | |
| 2.6.4 | 18 / 11 | |
| 2.6.3 | 18 / 11 | |
| 2.6.2 | 18 / 11 | |
| 2.6.1 | 18 / 11 | |
| 2.6.0 | 18 / 11 | |
| 2.5.1 | 18 / 11 | |
| 2.5.0 | 18 / 11 | |
| 2.4.0 | 18 / 11 | |
| 2.3.0 | 18 / 11 | |
| 2.2.1 | 18 / 11 | |
| 2.2.0 | 18 / 11 | |
| 2.1.0 | 18 / 11 | |
| 2.0.0 | 17 / 11 | |
| 1.4.0 | 10 / 10 | |
| 1.3.0 | 11 / 10 | |
| 1.2.3 | 11 / 10 | |
| 1.2.2 | 11 / 10 | |
| 1.2.1 | 11 / 10 | |
| 1.2.0 | 11 / 10 | |
| 1.1.2 | 11 / 10 | |
| 1.1.1 | 11 / 10 | |
| 1.1.0 | 11 / 10 | |
| 1.0.4 | 11 / 10 | |
| 1.0.3 | 11 / 10 | |
| 1.0.2 | 11 / 10 |
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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.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.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.