react-jsonschema-form — Greenflagged

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

ametaireauedi9999epicfaaceglassercleplatremmagopiann1k0natimpeterbe

Keywords

reactformjson-schema

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change n1k0→glasserc in 2017 reflects a legitimate Mozilla team maintainer transition; glasserc has 52 approved packages and 0 rejected. Stable for this package.	ai	2026/04/24
source-diff	obfuscated-file:dist/editor.worker.js	AI (source-diff): Monaco Editor webpack worker bundle — standard minified webpack IIFE output with accompanying source map. Not obfuscation; legitimate build artifact for this package.	ai	2026/04/24
source-diff	obfuscated-file:dist/json.worker.js	AI (source-diff): Monaco Editor JSON language worker bundle — standard minified webpack IIFE output with accompanying source map. Not obfuscation; legitimate build artifact for this package.	ai	2026/04/24
source-diff	net-exec-file:dist/json.worker.js	AI (source-diff): Monaco JSON worker uses web worker messaging and dynamic module loading by design. Pattern matches are false positives for this well-known language server worker bundle.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): core-js and babel-runtime are canonical Babel ecosystem polyfill/runtime packages; their addition is a standard build practice for this type of library, not a supply chain risk.	ai	2026/04/24

Versions (showing 51 of 101)

View all versions

Version	Deps	Published
1.8.1	8 / 53	2019-12-16
1.8.0	8 / 53	2019-08-26
1.7.0	10 / 50	2019-07-16
1.6.1	6 / 49	2019-06-08
1.6.0	6 / 49	2019-06-06
1.5.0	5 / 49	2019-04-17
1.4.1	5 / 49	2019-04-17
1.4.0	5 / 49	2019-04-04
1.3.0	5 / 49	2019-03-06
1.2.1	5 / 49	2019-02-04
1.2.0	5 / 49	2019-01-14
1.1.0	5 / 49	2019-01-10
1.0.7	5 / 49	2019-01-10
1.0.6	5 / 49	2018-11-09
1.0.5	5 / 48	2018-10-01
1.0.4	5 / 48	2018-07-27
1.0.3	4 / 47	2018-04-12
1.0.2	4 / 47	2018-03-09
1.0.1	4 / 47	2018-02-07
1.0.0	4 / 47	2017-10-24
0.51.0	4 / 42	2017-10-09
0.50.1	4 / 42	2017-09-07
0.50.0	4 / 42	2017-09-06
0.49.0	4 / 42	2017-06-08
0.48.2	4 / 43	2017-05-07
0.48.1	4 / 43	2017-05-07
0.48.0	3 / 44	2017-04-28
0.47.0	3 / 44	2017-04-25
0.46.0	3 / 43	2017-04-07
0.45.0	3 / 43	2017-03-23
0.44.0	3 / 43	2017-03-21
0.43.0	3 / 39	2017-02-22
0.42.0	3 / 39	2017-01-28
0.41.2	3 / 39	2016-11-25
0.41.1	2 / 39	2016-11-09
0.41.0	2 / 39	2016-11-09
0.40.0	2 / 37	2016-08-30
0.39.0	2 / 37	2016-08-19
0.38.1	2 / 37	2016-08-16
0.38.0	2 / 37	2016-07-11
0.37.0	2 / 37	2016-07-07
0.36.1	2 / 37	2016-07-06
0.36.0	2 / 37	2016-07-06
0.35.1	3 / 37	2016-07-04
0.35.0	3 / 37	2016-06-30
0.34.1	3 / 37	2016-06-22
0.34.0	3 / 37	2016-06-20
0.33.3	3 / 37	2016-06-20
0.33.2	3 / 37	2016-06-09
0.33.1	3 / 37	2016-06-03
0.33.0	3 / 37	2016-06-02

v1.8.1

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.

v1.8.0

4 findings

HIGH New obfuscated file: dist/editor.worker.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/json.worker.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/json.worker.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.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.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.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.0

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

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.

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

v0.51.0

2 findings

HIGH Publisher changed: n1k0 → glasserc (on 2017-10-09) provenance

This version was published by a different npm account than previous versions on 2017-10-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.50.1

2 findings

HIGH Publisher changed: n1k0 → glasserc (on 2017-09-07) provenance

This version was published by a different npm account than previous versions on 2017-09-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.50.0

2 findings

HIGH Publisher changed: n1k0 → glasserc (on 2017-09-06) provenance

This version was published by a different npm account than previous versions on 2017-09-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.49.0

1 finding

LOW No provenance attestation provenance

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

v0.48.2

1 finding

LOW No provenance attestation provenance

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

v0.48.1

1 finding

LOW No provenance attestation provenance

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

v0.48.0

1 finding

LOW No provenance attestation provenance

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

v0.47.0

1 finding

LOW No provenance attestation provenance

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

v0.46.0

1 finding

LOW No provenance attestation provenance

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

v0.45.0

1 finding

LOW No provenance attestation provenance

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

v0.44.0

1 finding

LOW No provenance attestation provenance

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

v0.43.0

1 finding

LOW No provenance attestation provenance

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

v0.42.0

1 finding

LOW No provenance attestation provenance

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

v0.41.2

1 finding

LOW No provenance attestation provenance

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

v0.41.1

1 finding

LOW No provenance attestation provenance

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

v0.41.0

1 finding

LOW No provenance attestation provenance

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

v0.40.0

1 finding

LOW No provenance attestation provenance

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

v0.39.0

1 finding

LOW No provenance attestation provenance

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

v0.38.1

1 finding

LOW No provenance attestation provenance

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

v0.38.0

1 finding

LOW No provenance attestation provenance

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

v0.37.0

1 finding

LOW No provenance attestation provenance

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

v0.36.1

1 finding

LOW No provenance attestation provenance

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

v0.36.0

1 finding

LOW No provenance attestation provenance

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

v0.35.1

1 finding

LOW No provenance attestation provenance

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

v0.35.0

1 finding

LOW No provenance attestation provenance

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

v0.34.1

1 finding

LOW No provenance attestation provenance

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

v0.34.0

1 finding

LOW No provenance attestation provenance

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

v0.33.3

1 finding

LOW No provenance attestation provenance

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

v0.33.2

1 finding

LOW No provenance attestation provenance

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

v0.33.1

1 finding

LOW No provenance attestation provenance

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

v0.33.0

1 finding

LOW No provenance attestation provenance

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