Third-party Notices

Documentation build dependencies

The current documentation project directly declares these packages:

Package	Purpose	Upstream license
Astro	Static site framework	MIT
Starlight	Documentation theme and components	MIT
sharp	Image processing	Apache-2.0
Slidev CLI	Pitch-deck build tooling	MIT
Slidev default theme	Pitch-deck theme	MIT

The package lock records the exact installed versions, integrity hashes, and transitive dependency graph. The package manifest permits compatible updates for several direct dependencies, so this page alone is not a release bill of materials.

Release-specific notices must be generated and reviewed from the lockfile and the artifacts actually shipped in that release. They must include relevant transitive packages and preserve any required license text or attribution.

Candidate integrations are not dependencies

No distributed toolkit integrations yet

Azure Data Lab Toolkit has no released target provider, sample database, community tool, or software integration. Projects on the community pages are candidates only. They are not documentation build dependencies and retain their upstream ownership, support model, and terms.

A future release that downloads, bundles, generates, or redistributes an artifact must identify its version, owner, authoritative source, license or usage terms, attribution, integrity evidence, and material restrictions in release-specific notices.

See Licensing, Tools And Solution Packs, and Sample And Data Sources.

The predecessor project has its own Azure SQLVM Toolkit third-party notices.