🎯 Use case
This file lives under “utils/”, which covers cross-cutting helpers (shell, tempfiles, settings, messages, process input, …). On the API surface it exposes getManagedPluginNames — mainly functions, hooks, or classes. It composes internal code from settings (relative imports).
Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.
🧠 Inline summary
import { getSettingsForSource } from '../settings/settings.js' /** * Plugin names locked by org policy (policySettings.enabledPlugins). *
📤 Exports (heuristic)
getManagedPluginNames
🖥️ Source preview
import { getSettingsForSource } from '../settings/settings.js'
/**
* Plugin names locked by org policy (policySettings.enabledPlugins).
*
* Returns null when managed settings declare no plugin entries (common
* case — no policy in effect).
*/
export function getManagedPluginNames(): Set<string> | null {
const enabledPlugins = getSettingsForSource('policySettings')?.enabledPlugins
if (!enabledPlugins) {
return null
}
const names = new Set<string>()
for (const [pluginId, value] of Object.entries(enabledPlugins)) {
// Only plugin@marketplace boolean entries (true OR false) are
// protected. Legacy owner/repo array form is not.
if (typeof value !== 'boolean' || !pluginId.includes('@')) {
continue
}
const name = pluginId.split('@')[0]
if (name) {
names.add(name)
}
}
return names.size > 0 ? names : null
}