@theia/ai-llamafile
Theia - Llamafile Integration
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Llamafile manager legitimately spawns local LLM processes; child_process use is expected and documented for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.73.1 | 4 / 1 | |
| 1.73.0 | 4 / 1 | |
| 1.72.3 | 4 / 1 | |
| 1.72.2 | 4 / 1 | |
| 1.72.1 | 4 / 1 | |
| 1.72.0 | 4 / 1 | |
| 1.71.2 | 4 / 1 | |
| 1.70.2 | 4 / 1 | |
| 1.61.0 | 4 / 1 | |
| 1.60.2 | 4 / 1 | |
| 1.60.1 | 4 / 1 | |
| 1.60.0 | 4 / 1 | |
| 1.59.0 | 4 / 1 | |
| 1.58.5 | 4 / 1 | |
| 1.58.4 | 4 / 1 | |
| 1.58.3 | 4 / 1 | |
| 1.58.2 | 4 / 1 | |
| 1.58.1 | 4 / 1 | |
| 1.58.0 | 4 / 1 | |
| 1.57.1 | 4 / 1 | |
| 1.57.0 | 4 / 1 | |
| 1.56.0 | 4 / 1 | |
| 1.55.1 | 4 / 1 | |
| 1.55.0 | 4 / 1 |
v1.73.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.60.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sgraband) than the most recent previously approved version (tsmaeder) on 2025-02-27, but sgraband is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.58.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tsmaeder) than the most recent previously approved version (jfaltermeier) on 2025-02-17, but tsmaeder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jfaltermeier) than the most recent previously approved version (sgraband) on 2024-12-16, but jfaltermeier is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.