@interfere/react
Client-side React SDK for Interfere. Error tracking, session replay, and analytics.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): OTel exporters likely configured at runtime/via config; stable false positive for this observability SDK. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-metrics-otlp-http | AI (phantom-deps): OTel exporters likely configured at runtime/via config; stable false positive for this observability SDK. | ai | |
| source-diff | obfuscated-file:dist/sw.mjs | AI (source-diff): Auto-generated minified Workbox SW bundle; comment and build script confirm legitimate provenance. | ai | |
| phantom-deps | phantom-dep:workbox-routing | AI (phantom-deps): Bundled into SW script via build-sw.ts, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:workbox-strategies | AI (phantom-deps): Bundled into SW script via build-sw.ts, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:workbox-background-sync | AI (phantom-deps): Bundled into SW script via build-sw.ts, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-logs-otlp-http | AI (phantom-deps): OTel exporters likely configured at runtime/via config; stable false positive for this observability SDK. | ai | |
| phantom-deps | phantom-dep:@fingerprintjs/fingerprintjs-pro | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level. | ai | |
| phantom-deps | phantom-dep:@ua-parser-js/pro-enterprise | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level. | ai | |
| phantom-deps | phantom-dep:tctx | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level, not directly imported in this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level. | ai | |
| phantom-deps | phantom-dep:rrweb | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Monorepo catalog dependency; resolved at workspace level. | ai | |
| phantom-deps | phantom-dep:@interfere/types | AI (phantom-deps): Same-org workspace dependency; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@interfere/constants | AI (phantom-deps): Same-org workspace dependency; stable false positive for this monorepo package. | ai | |
| dependencies | unvetted-dep:tctx | AI (dependencies): tctx is a small trace-context propagation library; its use here as a dependency is benign and consistent with observability SDK purpose. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance attestation but no other risk signals; consistent across all versions. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 32 / 15 | |
| 9.0.2 | 6 / 14 | |
| 9.0.1 | 6 / 14 | |
| 9.0.0 | 6 / 14 | |
| 8.1.6 | 6 / 14 | |
| 8.1.2 | 6 / 15 | |
| 8.1.1 | 6 / 15 | |
| 8.1.0 | 6 / 15 | |
| 8.0.0 | 6 / 16 | |
| 7.0.0 | 6 / 16 | |
| 6.0.0 | 6 / 16 | |
| 5.0.1 | 6 / 16 | |
| 5.0.0 | 6 / 16 | |
| 4.0.0 | 7 / 16 | |
| 3.0.0 | 7 / 16 | |
| 1.0.3 | 8 / 16 | |
| 1.0.2 | 8 / 16 | |
| 1.0.1 | 8 / 16 | |
| 1.0.0 | 8 / 16 |
v10.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.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.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v4.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.
v3.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.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.