I'd like to request access to the current userscript's native UUID through GM_info.uuid and the equivalent GM.info.uuid property.
ScriptCat already maintains a UUID for each installed script. Exposing that existing identifier would give userscript developers a stable, documented way to identify the current installation during execution, without inspecting generated source code, editor URLs, or internal extension storage.
Suggested API:
const scriptUuid = GM_info.uuid;
// Equivalent alias:
const sameUuid = GM.info.uuid;
This would help developers:
- Distinguish installed script instances without relying on names, versions, or URLs.
- Coordinate work across tabs and execution contexts belonging to the same installation.
- Build reusable libraries with consistent script identification.
- Improve diagnostics and instance-specific state management.
- Align with Violentmonkey, which already exposes
GM_info.uuid.
The value should be the UUID ScriptCat already assigns to the current script, remain stable across page reloads and normal script updates, and be available wherever GM_info is provided. Access should be limited to the current script's identifier and require no additional permissions. It would not expose a hardware or browser-wide identifier.
It would also be helpful to document how the identifier behaves when scripts are duplicated, reinstalled, imported, restored, or synchronized, and include the property in ScriptCat's TypeScript definitions.
Reference: Violentmonkey GM_info documentation.
Thank you for considering this addition.
I'd like to request access to the current userscript's native UUID through
GM_info.uuidand the equivalentGM.info.uuidproperty.ScriptCat already maintains a UUID for each installed script. Exposing that existing identifier would give userscript developers a stable, documented way to identify the current installation during execution, without inspecting generated source code, editor URLs, or internal extension storage.
Suggested API:
This would help developers:
GM_info.uuid.The value should be the UUID ScriptCat already assigns to the current script, remain stable across page reloads and normal script updates, and be available wherever
GM_infois provided. Access should be limited to the current script's identifier and require no additional permissions. It would not expose a hardware or browser-wide identifier.It would also be helpful to document how the identifier behaves when scripts are duplicated, reinstalled, imported, restored, or synchronized, and include the property in ScriptCat's TypeScript definitions.
Reference: Violentmonkey GM_info documentation.
Thank you for considering this addition.