@rnacanvas/forms.find No license 41 versions

@rnacanvas/forms.find

npm Repository Homepage

41

Versions

—

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

pzhaojohnson

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@rnacanvas/math	AI (phantom-deps): Same-org dep; bundled dist pattern causes phantom-dep false positives for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@rnacanvas/boxes	AI (phantom-deps): Same-org dep; bundled dist pattern causes phantom-dep false positives for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@rnacanvas/forms	AI (phantom-deps): Same-org dep; bundled dist pattern causes phantom-dep false positives for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@rnacanvas/utilities	AI (phantom-deps): Same-org dep; bundled dist pattern causes phantom-dep false positives for this package.	ai	2026/05/06
phantom-deps	phantom-dep:@rnacanvas/value-check	AI (phantom-deps): Same-org dep; bundled dist pattern causes phantom-dep false positives for this package.	ai	2026/05/06
phantom-deps	phantom-dep:jquery	AI (phantom-deps): jquery is a declared runtime dep used in UI forms; referenced in config is expected for this package type.	ai	2026/05/06

Versions (showing 41 of 41)

Version	Deps	Published
4.2.2	8 / 13	2026-06-06
4.2.1	8 / 13	2026-06-06
4.2.0	8 / 13	2026-06-06
4.1.0	8 / 13	2026-05-17
4.0.0	8 / 13	2026-05-17
3.2.5	8 / 13	2026-04-23
3.2.4	8 / 13	2026-04-04
3.2.3	8 / 13	2026-04-04
3.2.2	8 / 13	2026-04-04
3.2.1	8 / 13	2026-04-04
3.2.0	8 / 13	2026-04-03
3.1.0	8 / 13	2026-04-03
3.0.5	8 / 13	2026-03-31
3.0.4	8 / 13	2026-03-31
3.0.3	8 / 13	2026-03-31
3.0.2	8 / 13	2026-03-30
3.0.1	8 / 13	2026-03-30
3.0.0	8 / 13	2026-03-30
2.0.6	8 / 13	2026-03-30
2.0.5	8 / 13	2026-03-30
2.0.4	8 / 13	2026-03-30
2.0.3	8 / 13	2026-03-30
2.0.2	8 / 13	2026-03-30
2.0.1	8 / 13	2026-03-30
2.0.0	8 / 13	2026-03-30
1.5.0	8 / 13	2026-03-30
1.4.3	8 / 13	2026-03-29
1.4.2	8 / 13	2026-03-29
1.4.1	8 / 13	2026-03-29
1.4.0	8 / 13	2026-03-29
1.3.0	8 / 13	2026-03-28
1.2.6	8 / 13	2026-03-28
1.2.5	8 / 13	2026-03-28
1.2.4	8 / 13	2026-03-28
1.2.3	8 / 13	2026-03-28
1.2.2	8 / 13	2026-03-28
1.2.1	8 / 13	2026-03-11
1.2.0	8 / 13	2026-03-10
1.1.2	8 / 13	2026-03-08
1.1.1	8 / 13	2026-03-08
1.1.0	8 / 13	2026-03-08

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

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

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

1 finding

LOW No provenance attestation provenance

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

v3.2.3

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.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.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

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

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

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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.