@panneau/modal-upload
File upload modal
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@uppy/dashboard | AI (dependencies): @uppy/dashboard is a well-known open-source Uppy component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Monorepo build artifact; lodash-es is a common utility dep, likely used transitively or in bundled output. | ai | |
| phantom-deps | phantom-dep:@uppy/file-input | AI (phantom-deps): Uppy plugin declared as dep; may be dynamically loaded or re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@uppy/progress-bar | AI (phantom-deps): Uppy plugin declared as dep; same pattern as other @uppy/* phantom-dep findings in this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared as dep, referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@panneau/uppy | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@uppy/utils | AI (phantom-deps): Declared as dep, referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Declared as dep, referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@panneau/core | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 10 / 2 | |
| 4.0.50 | 10 / 2 | |
| 4.0.48 | 10 / 2 | |
| 4.0.41 | 10 / 2 | |
| 4.0.39 | 10 / 2 | |
| 4.0.38 | 10 / 2 | |
| 4.0.37 | 10 / 2 | |
| 4.0.36 | 10 / 2 | |
| 4.0.15 | 10 / 2 | |
| 4.0.14 | 10 / 2 | |
| 4.0.11 | 11 / 2 | |
| 4.0.8 | 11 / 2 | |
| 4.0.7 | 11 / 2 | |
| 4.0.6 | 11 / 2 | |
| 4.0.5 | 11 / 2 | |
| 4.0.4 | 11 / 2 | |
| 4.0.2 | 11 / 2 | |
| 4.0.1 | 11 / 2 | |
| 4.0.0 | 11 / 2 | |
| 3.0.314 | 11 / 2 | |
| 3.0.310 | 11 / 2 | |
| 3.0.308 | 14 / 2 | |
| 3.0.307 | 14 / 2 |
v4.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.310
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.