REVIEW 2 cited by
Large Language Model Supply Chain: A Research Agenda
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
The rapid advancement of large language models (LLMs) has revolutionized artificial intelligence, introducing unprecedented capabilities in natural language processing and multimodal content generation. However, the increasing complexity and scale of these models have given rise to a multifaceted supply chain that presents unique challenges across infrastructure, foundation models, and downstream applications. This paper provides the first comprehensive research agenda of the LLM supply chain, offering a structured approach to identify critical challenges and opportunities through the dual lenses of software engineering (SE) and security & privacy (S\&P). We begin by establishing a clear definition of the LLM supply chain, encompassing its components and dependencies. We then analyze each layer of the supply chain, presenting a vision for robust and secure LLM development, reviewing the current state of practices and technologies, and identifying key challenges and research opportunities. This work aims to bridge the existing research gap in systematically understanding the multifaceted issues within the LLM supply chain, offering valuable insights to guide future efforts in this rapidly evolving domain.
Forward citations
Cited by 2 Pith papers
-
Toward Understanding Bugs in Vector Database Management Systems
A manual study of 1,463 confirmed bugs in 15 vector database systems yields a taxonomy of 5 symptom categories, 31 root causes, and 12 fix strategies.
-
An Empirical Study of Vulnerable Package Dependencies in LLM Repositories
In 52 open-source LLM projects, 75.8% of those with dependency configs use at least one vulnerable package, and half of supply chain vulnerabilities stay undisclosed for over 56 months.
Discussion (0). Sign in to comment.