@unisphere/dev
Local development server for the Unisphere ecosystem
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/client/assets/index-CvColpAg.js | AI (source-diff): Vite-bundled React client asset; standard minified build output for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-D6mF3iRu.js | AI (source-diff): Vite-bundled React client asset; minification is expected for this package's client UI build output. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Cf-6uRgv.js | AI (source-diff): Standard Vite-bundled React client asset; minification is expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DDjL5KRh.js | AI (source-diff): Vite-bundled React client asset; minification is expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DC1yrJxY.js | AI (source-diff): Vite-bundled React client bundle; minification is expected for this dev-server UI package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-C_Zi6nKq.js | AI (source-diff): Vite-bundled React client asset; minification is expected for this package's build output. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI publish for kaltura org. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-B43K663f.js | AI (source-diff): Standard Vite/React minified bundle; expected build artifact for this dev-server package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CipQKMvF.js | AI (source-diff): Vite-bundled React client asset; minification is expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-9nMLcZ35.js | AI (source-diff): Vite-minified React bundle; consistent with declared build pipeline (vite+react). Expected for this package. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @unisphere/dev is a Kaltura dev-server tool; Levenshtein match to 'ajv' is coincidental and not a typosquat. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.3.5 | 4 / 19 | |
| 3.3.4 | 4 / 19 | |
| 3.3.3 | 4 / 19 | |
| 3.3.2 | 4 / 19 | |
| 3.3.0 | 4 / 19 | |
| 3.2.1 | 4 / 19 | |
| 3.2.0 | 4 / 19 | |
| 3.1.1 | 4 / 19 | |
| 3.1.0 | 4 / 19 | |
| 3.0.2 | 4 / 19 | |
| 3.0.1 | 4 / 19 | |
| 3.0.0 | 4 / 19 | |
| 2.2.0 | 4 / 19 | |
| 2.1.1 | 4 / 19 | |
| 1.1.1 | 4 / 19 | |
| 1.1.0 | 4 / 19 | |
| 0.1.0 | 2 / 18 |
v3.3.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
3 findingsThis version was published by a different npm account than previous versions on 2026-04-27. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
3 findingsThis version was published by a different npm account than previous versions on 2026-04-21. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
3 findingsThis version was published by a different npm account than previous versions on 2026-04-21. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.