@qontinui/ui-bridge
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/types-MSDXO1YO.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled type defs; not executable code. | ai | |
| source-diff | obfuscated-file:dist/types-DOBfNUEe.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type defs; not executable code. | ai | |
| source-diff | obfuscated-file:dist/types-Bh8GMnD9.d.ts | AI (source-diff): Same pattern as .d.mts counterpart — bundled type declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-Bue5gWo6.d.mts | AI (source-diff): TypeScript declaration rollup file with readable JSDoc comments; long lines are bundler artifact, not obfuscation. | ai | |
| npm-metadata | url-dep:@qontinui/ui-bridge-auto | AI (npm-metadata): file: path in devDependencies is a monorepo workspace reference; not shipped to consumers. | ai | |
| source-diff | obfuscated-file:dist/types-CzK_r8H4.d.mts | AI (source-diff): Long lines in bundled TypeScript declaration rollup files are expected; not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with SLSA provenance attestation via CI/CD pipeline. | ai | |
| source-diff | obfuscated-file:dist/types-BAhw9LhP.d.mts | AI (source-diff): TypeScript declaration rollup; long lines are concatenated type definitions, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-BAhw9LhP.d.ts | AI (source-diff): TypeScript declaration rollup; long lines are concatenated type definitions, not obfuscated code. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 1 / 14 | |
| 0.11.0 | 1 / 14 | |
| 0.9.1 | 1 / 14 | |
| 0.8.5 | 1 / 14 | |
| 0.8.3 | 1 / 14 | |
| 0.8.2 | 1 / 14 | |
| 0.8.1 | 1 / 14 | |
| 0.8.0 | 1 / 14 | |
| 0.7.0 | 1 / 14 | |
| 0.3.2 | 0 / 14 | |
| 0.2.0 | 0 / 9 | |
| 0.1.1 | 0 / 9 |
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
4 findingsThis version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
4 findingsThis version was published by a different npm account than previous versions on 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.