SAIF.Data has a single internal project reference to SAIF.Data.Guidewire for its HTTP client infrastructure, a wide surface of external NuGet packages spanning the SAIF.Framework family, NHibernate, Autofac, Polly, and JSON handling, and several referenced-but-unused packages surfaced by Stage 1 analysis (saif-data-analysis.md).
Supplies the Guidewire HttpClientBase, IDataClientConfiguration/DataClientConfiguration, and the Guidewire clients registered by AddDataClients (saif-data-analysis.md Dependencies)
AutoMapper, FluentValidation, RestSharp, System.Data.OracleClient, and SAIF.Web.API.Clients are referenced but no substantive usage was confirmed during the Stage 1 scan (saif-data-analysis.md Open questions item 7)*.
TestRepository/** seeding helpers ship in the production NuGet package; whether that is intentional is unknown (saif-data-analysis.md Open questions item 5)**.
Query provider registration and lifetimes are decided outside this library, for example in DependencyMaps/*, so the effective DI graph cannot be fully verified from this repository alone (saif-data-analysis.md Architecture findings)*.
Credentials for HttpClientBase are decrypted using SystemHashUtil and split on | without a length check; a malformed secure setting throws IndexOutOfRangeException rather than a descriptive error (saif-data-config-analysis.md Secure settings catalog)*.
HttpClientBase.GetAsyncCached caches responses process-wide for a default 30 seconds with no per-user key component, so per-user data-level filtering applied downstream is not reflected in the cache (saif-data-security-analysis.md Security concerns, Medium severity)*.
The obsolete CCClaimApiService constructor's baseUrlOverride argument is silently ignored by the Guidewire base class; the URL always comes from cc.ccclaimdataapiurl (saif-data-config-analysis.md notes).