@hyperse/inspector
@hyperse/inspector is the tool for seamlessly navigating from your browser to your IDE. With just a simple click, you can jump from a React component in the browser to its source code in your local IDE instantly. Think of it as a supercharged version of C
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; provenance absence is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:@hyperse/tinykeys | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly within the monorepo bundle. | ai | |
| phantom-deps | phantom-dep:@types/react-reconciler | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported at runtime. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 4 / 14 | |
| 2.0.2 | 4 / 14 | |
| 2.0.1 | 4 / 14 | |
| 2.0.0 | 4 / 14 |
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.