Driver Verification Policy

Sources

Drivers enter the database exclusively from official distribution channels: Microsoft Update Catalog and the public catalogs of hardware manufacturers (currently Dell, Lenovo and NVIDIA). We do not accept user uploads and do not mirror third-party driver sites.

What we verify

• File integrity. For verified entries we download the actual file from the official source and compute its SHA-256 checksum. The checksum on the driver page lets you confirm your download is identical.
• Package contents. We unpack driver archives and parse the INF file: signing date, provider, device class, catalog (signature) file and the full list of files inside the package.
• Hardware compatibility. Supported Hardware IDs are extracted from both the source catalog and the INF itself, and indexed for search.

What the badges mean

SHA-256 verified- we downloaded this exact file and published its checksum, INF metadata and contents. Entries without the badge carry catalog metadata and an official link, but we haven't hashed the file yet.

Quality gate

A driver page is published only when it identifies the hardware it supports and carries verifiable data (a release date from the source catalog, or a hashed file). Records that don't meet the bar stay out of the index until completed. We never invent missing values.