@devframes/plugin-code-server
Run VS Code in the browser (code-server, code serve-web, or a tunnel) as a devframe panel — detect a local install, launch it on demand, and embed the editor in an auto-authenticated iframe.
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/spa/assets/index-CkuBbEzE.js | AI (source-diff): Vite-bundled SPA asset, not true obfuscation; consistent with package's build tooling. | ai | |
| source-diff | obfuscated-file:dist/spa/assets/index-BBK8liCe.js | AI (source-diff): Vite build banner/minified SPA output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/spa/assets/index-CT2PEkxJ.js | AI (source-diff): Vite/Vue bundled SPA asset, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/spa/assets/index-YDI4bJsV.js | AI (source-diff): Vite build output (modulepreload polyfill), not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/spa/assets/index-7eFiM-n1.js | AI (source-diff): Vite/Vue bundled SPA build output, not obfuscation; no malicious behavior in sample. | ai | |
| source-diff | obfuscated-file:dist/spa/assets/index-DbI4Lf4T.js | AI (source-diff): Vite/Rollup bundled SPA output, not obfuscation; matches build script. | ai | |
| phantom-deps | phantom-dep:cac | AI (phantom-deps): cac used by CLI bin.mjs; bundled/minified, common false positive. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.7.14 | 3 / 16 | |
| 0.7.13 | 3 / 16 | |
| 0.7.12 | 3 / 16 | |
| 0.7.11 | 3 / 16 | |
| 0.7.10 | 3 / 16 | |
| 0.7.9 | 3 / 16 | |
| 0.7.8 | 3 / 16 | |
| 0.7.7 | 3 / 16 | |
| 0.7.6 | 3 / 16 | |
| 0.7.5 | 4 / 13 | |
| 0.7.4 | 4 / 13 | |
| 0.7.3 | 4 / 13 | |
| 0.7.2 | 4 / 13 | |
| 0.7.0 | 4 / 13 | |
| 0.6.2 | 3 / 13 | |
| 0.6.1 | 3 / 13 | |
| 0.6.0 | 3 / 13 | |
| 0.0.1 | 3 / 13 |
v0.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.13
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.7.12
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.7.11
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.7.10
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.7.9
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.7.8
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.7.7
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.7.6
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.7.5
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.7.4
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.7.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.7.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.7.0
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.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.