Dimension scores are derived from public data and fields; weighted into the composite. Reference only.
permission.site is a browser permission testing page designed for web development and testing scenarios. It is not an IDE, SDK, or cloud service in the traditional sense. Instead, it uses a set of buttons to trigger browser permissions and Web API behaviors, helping developers observe permission prompts and capability support across different browsers, protocols, and system environments.
Based on the captured content, it covers a very wide range of test items, including Notifications, Location, Camera, Microphone, Screen Share, MIDI, Bluetooth, USB, Serial, HID, Encrypted Media, Idle Detection, Persistent Storage, Open File Picker, Directory Picker, Protocol Handler, WebAuthn Attestation, NFC, VR/AR, Device Orientation/Motion, Fullscreen, Pointer Lock, Keyboard Lock, Copy, Auto Download, Popup, and the Async Clipboard API. For frontend developers and QA teams, this kind of tool is useful for reproducing permission dialogs, verifying HTTPS restrictions, and checking whether experimental Web Platform APIs are available.
The page content does not mention specific programming languages or frameworks, nor does it describe any SDK/API. It mainly relies on native browser Web APIs, so it is better understood as a test collection for Web Platform capabilities. The page shows “On GitHub,” suggesting that the source code may be available, but the captured text does not provide a license, maintainer information, or an open-source agreement, so its open-source status cannot be determined directly. In terms of ecosystem integration, it relates to browser capabilities such as Chrome experimental flags, WebAuthn security keys, Async Clipboard, and EME, but there is no indication of third-party service integrations.
No pricing, subscription, or commercial edition information appears on the page, so based on the available text it can be regarded as a free tool. As for documentation, there are only a few Notes, such as AR requiring chrome://flags/#enable-experimental-web-platform-features to be enabled, Async Clipboard being available only on secure connections, and WebAuthn possibly requiring a touch on a security key. These hints are practical, but they do not amount to full documentation, and the site lacks a browser compatibility matrix and detailed troubleshooting guide.
Its strengths are broad permission coverage, straightforward operation, and suitability for quick verification. Its limitations are that it is mainly geared toward manual testing and lacks automation interfaces, release notes, and support commitments. It is suitable for frontend engineers, browser compatibility testers, QA engineers, and learners exploring Web APIs.
The captured content does not provide access, network node, or payment information, so the stability of direct access from mainland China cannot be determined and should be treated as unknown. If access is unstable, alternatives include MDN examples, Chrome DevTools, web.dev demos, or writing your own permission testing page.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on permission.site official site.
permission.site is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of China direct-connect friendly. Click "Visit Official Site" to reach permission.site directly.