Who is Inspections for Google™ Closure for?

Inspections for Google™ Closure is a B2B product built for developers using IntelliJ-based IDEs and Google Closure.

Is Inspections for Google™ Closure free?

Yes — Inspections for Google™ Closure is free to use.

What platforms does Inspections for Google™ Closure run on?

Inspections for Google™ Closure runs on the web, macOS, Windows, and Linux.

Is Inspections for Google™ Closure still maintained?

Unverified. Inspections for Google™ Closure has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.

What are alternatives to Inspections for Google™ Closure?

Similar projects tracked by PulseGate include Closure Linter, Google Closure Soy Templates, and Custom Inspections.

Who makes Inspections for Google™ Closure?

Inspections for Google™ Closure is developed by JetBrains.

How long has Inspections for Google™ Closure been around?

Inspections for Google™ Closure first shipped in 2019.

Back to the index

Inspections for Google™ Closure

Name: Inspections for Google™ Closure
Author: JetBrains

jetbrains.comOther dev tools

Inspections for Google Closure is a plugin for IntelliJ-based IDEs that adds inspections for Google Closure code. It helps developers identify coding issues and improve code quality while working in supported JetBrains IDEs.

FreeWebmacOSWindowsLinux

Visit jetbrains.com

Overview

4 features

Inspections for Google™ Closure sits in PulseGate's Other dev tools category. It focuses on finding and correcting Google Closure code issues within IntelliJ-based IDEs. It is built as a B2B product for developers using IntelliJ-based IDEs and Google Closure. Inspections for Google™ Closure is free to use. It runs on the web, macOS, Windows, and Linux.

JetBrains builds and maintains Inspections for Google™ Closure, and it first shipped in 2019. Among its 4 catalogued features are code inspections, Google Closure support, and IDE integration.

Summary written by a language model from the project’s public pages.

Code inspections
Google Closure support
IDE integration
Code quality checks

Built with & integrations

Hosting

AWS

Connectors

vscode

Runs on

BrowsermacOSWindowsLinux

Detected from

AWS: x-amz-cf-id header · x-amz-cf-pop header · via header

Trust & compliance

Verified signals

HTTPSFree tier

Indexing history

What PulseGate has recorded for this listing

Indexed8 Sept · 15:41 UTC
Inspections for Google™ Closure verified via JetBrains Plugins
Source: JetBrains Plugins · Open

Frequently asked questions about Inspections for Google™ Closure

What is Inspections for Google™ Closure?: Inspections for Google™ Closure focuses on finding and correcting Google Closure code issues within IntelliJ-based IDEs. It is catalogued under Other dev tools on PulseGate.
Who is Inspections for Google™ Closure for?: Inspections for Google™ Closure is a B2B product built for developers using IntelliJ-based IDEs and Google Closure.
Is Inspections for Google™ Closure free?: Yes — Inspections for Google™ Closure is free to use.
What platforms does Inspections for Google™ Closure run on?: Inspections for Google™ Closure runs on the web, macOS, Windows, and Linux.
Is Inspections for Google™ Closure still maintained?: Unverified. Inspections for Google™ Closure has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to Inspections for Google™ Closure?: Similar projects tracked by PulseGate include Closure Linter, Google Closure Soy Templates, and Custom Inspections.Closure Linter Google Closure Soy Templates Custom Inspections
Who makes Inspections for Google™ Closure?: Inspections for Google™ Closure is developed by JetBrains.
How long has Inspections for Google™ Closure been around?: Inspections for Google™ Closure first shipped in 2019.

At a glance

Platforms: Web
Languages: English
First seen: 8 Sept 2026
Built for: developers using IntelliJ-based IDEs and Google Closure
Model: B2B
Solves: Finding and correcting Google Closure code issues within IntelliJ-based IDEs.

Registered as

JetBrains Marketplace: 10725

Developer

JetBrains

Index record

Indexed: 8 Sept 2026
Lifecycle: Alive
First seen: Sept 2026
Last seen: 8 Sept 2026

Identity audit (13)

Slug: inspections-for-googletm-closure-jetbrains-com
Lifecycle state recorded: 8 Sept 2026
Verification state: Indexed for public listing
Listing state: Listed: yes
Index status: Included in index
Latest evidence snapshot: 8 Sept 2026
Timeline basis: Indexed-at chronology (no inferred launch/funding milestones).
Name from: Derived from the project's own page and URL.
Category from: Assigned by a language model.
Summary from: Written by a language model from public pages.
Languages from: Detected by a language model from page content.
Last updated: 8 Sept 2026
Canonical URL: https://plugins.jetbrains.com/plugin/10725-inspections-for-google-closure

Ship this? Send a correction — no account, and you get a link to follow it.

Similar projects

Closest matches by what these projects do