@panneau/field-upload ISC 34 versions

@panneau/field-upload

npm Repository Homepage

An Upload field

34

Versions

ISC

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

phatshamblerfolklore-devdmongeau

Keywords

javascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@uppy/file-input	AI (phantom-deps): Referenced in config/build files for this upload field package; stable false positive.	ai	2026/05/07
phantom-deps	phantom-dep:@uppy/progress-bar	AI (phantom-deps): Referenced in config/build files for this upload field package; stable false positive.	ai	2026/05/07
phantom-deps	phantom-dep:@panneau/themes	AI (phantom-deps): Same-org CSS theme dep; referenced in build config, not JS imports — stable false positive.	ai	2026/05/02
phantom-deps	phantom-dep:@fortawesome/react-fontawesome	AI (phantom-deps): FontAwesome deps used via config/build pipeline; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@uppy/utils	AI (phantom-deps): Listed as dep, used transitively via @panneau/uppy; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@fortawesome/free-solid-svg-icons	AI (phantom-deps): FontAwesome deps used via config/build pipeline; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@fortawesome/fontawesome-svg-core	AI (phantom-deps): FontAwesome deps used via config/build pipeline; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:tailwindcss	AI (phantom-deps): CSS build tool referenced in config; not directly imported in JS — stable false positive.	ai	2026/05/02

Versions (showing 34 of 34)

Version	Deps	Published
4.0.55	19 / 2	2026-05-27
4.0.50	19 / 2	2026-05-14
4.0.48	19 / 2	2026-05-14
4.0.45	19 / 2	2026-05-14
4.0.41	19 / 2	2026-05-12
4.0.39	19 / 2	2026-04-29
4.0.34	19 / 2	2026-04-17
4.0.33	19 / 2	2026-04-14
4.0.31	19 / 2	2026-04-14
4.0.27	19 / 2	2026-03-12
4.0.26	19 / 2	2026-03-11
4.0.24	19 / 2	2026-03-06
4.0.23	19 / 2	2026-03-05
4.0.21	19 / 2	2026-03-04
4.0.20	19 / 2	2026-03-04
4.0.19	19 / 2	2026-03-03
4.0.18	19 / 2	2026-03-03
4.0.17	19 / 2	2026-03-03
4.0.8	20 / 2	2025-11-25
4.0.7	20 / 2	2025-11-21
4.0.6	20 / 2	2025-11-21
4.0.5	20 / 2	2025-11-20
4.0.4	20 / 2	2025-11-20
4.0.3	20 / 2	2025-11-20
4.0.2	20 / 2	2025-11-20
4.0.1	20 / 2	2025-11-20
4.0.0	20 / 2	2025-11-20
3.0.323	20 / 2	2026-04-24
3.0.322	20 / 2	2026-04-23
3.0.321	20 / 2	2026-04-23
3.0.314	20 / 2	2025-11-24
3.0.310	20 / 2	2025-11-14
3.0.308	23 / 2	2025-11-12
3.0.307	23 / 2	2025-11-06

v4.0.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.48

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.45

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.323

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.322

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.321

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.314

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.310

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.308

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.307

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.