@amsom-habitat/file-manager
Ce package regroupe plusieurs composants destinés à la gestion de fichiers et documents pour les outils d'AMSOM Habitat.
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 | encoded-string-file:dist/file-manager.umd.cjs | AI (source-diff): Encoded strings are FontAwesome SVG/font data and zlib-compressed CSS bundled by Vite — not malicious payloads. | ai | |
| source-diff | encoded-string-file:dist/file-manager.js | AI (source-diff): Same as UMD build: base64/zlib font and icon data from FontAwesome bundled by Vite. | ai | |
| source-diff | net-exec-file:dist/index.es-BkqYVoOB-DiaxpH-6.js | AI (source-diff): Function('return this')() is a standard cross-env global polyfill pattern from core-js, not a dropper. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/ui | AI (phantom-deps): Externalized peer dep bundled separately; phantom-dep is a false positive for this Vue component library. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Externalized dep in Vite build; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mime | AI (phantom-deps): Externalized dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jszip | AI (phantom-deps): Externalized dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:heic2any | AI (phantom-deps): Externalized dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pdf-merger-js | AI (phantom-deps): Externalized dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:moment-timezone | AI (phantom-deps): Externalized dep; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/html2canvas-CDGcmOD3-DO8r6Aun.js | AI (source-diff): Minified html2canvas library bundled by Vite; not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/file-utils | AI (phantom-deps): Same-org externalized dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/bootstrap-5 | AI (phantom-deps): Same-org externalized dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Externalized peer dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Externalized peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Externalized peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-brands-svg-icons | AI (phantom-deps): Externalized peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-regular-svg-icons | AI (phantom-deps): Externalized peer dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@amsom-habitat/date-utils | AI (phantom-deps): Same-org externalized dep; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/purify-BfsPID7W-C2k8hN99.js | AI (source-diff): Minified DOMPurify library bundled by Vite; not obfuscated malware. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.3.10 | 15 / 16 | |
| 1.3.9 | 15 / 16 | |
| 1.3.8 | 15 / 16 | |
| 1.3.7 | 15 / 16 | |
| 1.3.6 | 15 / 16 | |
| 1.3.5 | 15 / 16 | |
| 1.3.4 | 15 / 16 | |
| 1.3.2 | 15 / 16 | |
| 1.3.1 | 16 / 21 | |
| 1.3.0 | 16 / 21 | |
| 1.2.0 | 16 / 21 | |
| 1.1.4 | 16 / 21 | |
| 1.1.3 | 16 / 21 | |
| 1.1.2 | 16 / 21 | |
| 1.1.1 | 16 / 21 | |
| 1.0.1 | 16 / 21 | |
| 1.0.0 | 16 / 21 | |
| 0.3.2 | 15 / 21 | |
| 0.3.1 | 15 / 19 | |
| 0.3.0 | 15 / 18 | |
| 0.2.2 | 15 / 18 | |
| 0.2.1 | 15 / 18 | |
| 0.1.1 | 14 / 18 | |
| 0.1.0 | 14 / 18 | |
| 0.0.9 | 14 / 18 | |
| 0.0.8 | 14 / 18 | |
| 0.0.7 | 14 / 18 |
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.3.6
3 findingsModified file contains 8 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
3 findingsModified file contains 8 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
3 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 14 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
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.1.1
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.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.