Verify public API bytes, India Geopolitical Risk Monitor

This browser tool compares the declared public API files with the exact SHA-256 and byte lengths in the public API byte manifest.

Byte consistency, not authentication

The manifest is unsigned. Without a digest obtained independently of this website, a match proves only that same-origin files agree with the same-origin manifest. Even with an external digest, this page does not establish source truth, rights, finality, atomic hosting, security certification, or the authenticity of the JavaScript performing the check.

1. Inspect the manifest

The browser has not loaded the manifest.

Raw manifest SHA-256: loading…
Declared files: — files · —

2. Add an external anchor if you have one

Expected raw manifest SHA-256

Optional. Paste a 64-character digest obtained through an independent channel, or use #sha256=<digest> in the URL. The page never supplies its own digest as an independent anchor.

3. Fetch and compare the declared files

This is an explicit, on-demand check: 117 requests and about 6.9 MiB for the current manifest. Only the manifest is loaded before you press the button.

0 files checked.

No verification has run.

Manual verification without JavaScript

Download the raw manifest and calculate its SHA-256 with sha256sum public_api_byte_manifest.json (or shasum -a 256 on macOS). Compare that value with a digest obtained independently. Then download the listed files and compare each raw file with its declared bytes and sha256. A same-site manifest without an independent digest is not an authenticity check.