You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- equivalent to llms-index (direct array, no filtering)
52
+
48
53
**Analysis:**
49
54
50
55
-**Completeness:** ✅ Equal—both return the same list of supported versions.
51
56
-**Boolean vs enum:** The hal-index uses `supported: true`, a simple boolean. The releases-index only exposes `support-phase: "active"` (which hal-index also has), requiring knowledge of the enum vocabulary (active, maintenance, eol, preview, go-live).
52
57
-**Property naming:** The hal-index uses `select(.supported)` with dot notation. The releases-index requires `select(.["support-phase"] == "active")` with bracket notation and string comparison.
53
58
-**Query complexity:** The hal-index query is 30% shorter and more intuitive for someone unfamiliar with the schema.
54
59
55
-
**Winner:** hal-index (**17% smaller**); llms-index equivalent (direct array, no filtering)
56
-
57
-
**Note on URL length:** The hal-index currently uses long GitHub raw URLs (91 chars per URL). With equivalent short CDN URLs, the hal-index would be **4.4 KB**—31% smaller than releases-index.
58
-
59
60
### Target Framework Queries
60
61
61
62
#### Query: "What Android platform version does each supported .NET version target?"
-**Platform versioning:** Each .NET version targets a specific Android API level. This query reveals the progression: .NET 8 → Android 34, .NET 9 → Android 35, .NET 10 → Android 36.
94
112
-**Upgrade planning:** Knowing the platform version helps teams plan SDK requirements when upgrading .NET versions.
95
113
-**Discoverability:** The `target-frameworks-json` link makes this data accessible through HAL navigation.
96
114
97
-
**Winner:** hal-index only; llms-index equivalent
98
-
99
115
### CVE Queries for Latest Security Patch
100
116
101
117
#### Query: "What CVEs were fixed in the latest .NET 8.0 security patch?"
@@ -266,6 +282,31 @@ done
266
282
# 8.0 | 05 | dotnet-sdk | CVE-2025-26646
267
283
```
268
284
285
+
**llms-index:** Uses `_embedded.latest_patches` with `latest-security` link for direct access:
| Breaking changes by category | ✅ | ✅ | ❌ | hal-index only |
820
861
| OS package dependencies | ✅ | ✅ | ❌ | hal-index only |
@@ -869,4 +910,4 @@ The HAL `_embedded` pattern ensures that any data referenced within a document i
869
910
870
911
The hal-index schema is optimized for the queries that matter most to security operations, while maintaining cache coherency across CDN deployments. The use of boolean properties (`supported`) instead of enum comparisons (`support-phase == "active"`) reduces query complexity and eliminates the need to know the vocabulary of valid enum values. Counterintuitively, the deeper HAL link structure (`._links.self.href`) is more ergonomic than flat URL properties (`.["releases.json"]`) because consistent snake_case naming enables dot notation throughout the query path.
871
912
872
-
The llms-index provides additional efficiency for AI workloads by embedding `latest_patches[]` with direct `latest-security` links for each version. It is not suitable for mission-critical cloud-native scenarios due to its higher update frequency, but offers significant fetch savings for interactive AI assistants (e.g., 2.5x smaller for version-specific CVE queries by skipping the 20 KB version index fetch).
913
+
The llms-index provides additional efficiency for AI workloads by embedding `latest_patches[]` with direct `latest-security`and `latest-sdk`links for each version. It is not suitable for mission-critical cloud-native scenarios due to its higher update frequency, but offers significant fetch savings for interactive AI assistants (e.g., 2.5x smaller for version-specific CVE queries by skipping the 20 KB version index fetch).
0 commit comments