@scaleflex/asset-picker
Framework-agnostic Asset Picker for Scaleflex VXP DAM
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/asset-picker-CMsm4Ewp.cjs | AI (source-diff): Standard Vite build output with hashed chunk filenames; sample confirms readable minified code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/asset-picker-DjEmkrjk.cjs | AI (source-diff): Standard Vite minified bundle output; readable code structure visible in sample, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/asset-picker-B9yttjwn.cjs | AI (source-diff): Vite build output with hashed chunk filenames; minification is expected for this UI component library. | ai | |
| source-diff | obfuscated-file:dist/asset-picker-CU38pC-H.cjs | AI (source-diff): Standard Vite/Rollup minified bundle; long lines are expected for bundled output, no malicious patterns in sample. | ai | |
| source-diff | obfuscated-file:dist/asset-picker-C8E1ICe9.cjs | AI (source-diff): Standard Vite/Rollup minified bundle; content is readable minified JS with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/asset-picker-VQJy5L-w.cjs | AI (source-diff): Standard Vite/Rollup minified bundle; long lines are minification artifacts, not obfuscation. | ai | |
| phantom-deps | phantom-dep:i18next-http-backend | AI (phantom-deps): i18next-http-backend is loaded dynamically/via config; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:hls.js | AI (phantom-deps): hls.js is bundled into the dist output; phantom-dep heuristic fires because it's not directly imported in source. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 4 / 8 | |
| 1.1.0 | 4 / 8 | |
| 1.0.8 | 4 / 8 | |
| 1.0.4 | 2 / 8 | |
| 1.0.2 | 2 / 8 | |
| 0.2.18 | 2 / 7 | |
| 0.2.17 | 2 / 7 | |
| 0.2.13 | 2 / 7 | |
| 0.2.12 | 2 / 7 | |
| 0.2.5 | 2 / 7 | |
| 0.2.4 | 2 / 7 | |
| 0.2.3 | 2 / 7 | |
| 0.2.2 | 2 / 7 | |
| 0.2.1 | 2 / 7 | |
| 0.2.0 | 2 / 7 | |
| 0.1.0 | 2 / 7 |
v1.1.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.
v1.1.0
3 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.
This version was published by a different npm account (dmitry.stremous) than the most recent previously approved version (philipka) on 2026-05-25, but dmitry.stremous is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.8
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.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v0.2.18
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.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
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.
v0.2.12
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.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.