@panneau/form-normal ISC 26 versions

@panneau/form-normal

npm Repository Homepage

Default resource forms

26

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:@panneau/data	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@panneau/themes	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@panneau/field-fields	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@panneau/element-button	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Declared in dependencies; likely used transitively or in config; stable false positive.	ai	2026/05/02
phantom-deps	phantom-dep:react-intl	AI (phantom-deps): Declared in dependencies; likely used transitively or in config; stable false positive.	ai	2026/05/02

Versions (showing 26 of 26)

Version	Deps	Published
4.0.55	10 / 2	2026-05-27
4.0.50	10 / 2	2026-05-14
4.0.48	10 / 2	2026-05-14
4.0.46	10 / 2	2026-05-14
4.0.45	10 / 2	2026-05-14
4.0.41	10 / 2	2026-05-12
4.0.39	10 / 2	2026-04-29
4.0.34	10 / 2	2026-04-17
4.0.33	10 / 2	2026-04-14
4.0.27	10 / 2	2026-03-12
4.0.21	10 / 2	2026-03-04
4.0.20	10 / 2	2026-03-04
4.0.19	10 / 2	2026-03-03
4.0.18	10 / 2	2026-03-03
4.0.17	10 / 2	2026-03-03
4.0.8	11 / 2	2025-11-25
4.0.7	11 / 2	2025-11-21
4.0.6	11 / 2	2025-11-21
4.0.5	11 / 2	2025-11-20
4.0.4	11 / 2	2025-11-20
4.0.2	11 / 2	2025-11-20
4.0.1	11 / 2	2025-11-20
4.0.0	11 / 2	2025-11-20
3.0.314	11 / 2	2025-11-24
3.0.308	11 / 2	2025-11-12
3.0.307	11 / 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.46

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.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.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.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.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.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.