← Home

survey-react-ui

npm Repository Homepage

A free MIT-licensed React UI component that renders dynamic, interactive JSON-based forms and surveys. You can use it to collect responses from users and send them to your own database.

83
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tsv2013duodvk

Keywords

reactsurveyformsurveyjssurvey-libraryreact-componentform-renderingsurvey-rendererdynamic-forminteractive-formform-libraryform-managementquestionnairedata-collectiondata-validationform-validationinput-validationui-componentjsonjson-schemareact-schema-formsurvey-rendererclient-sidefrontendjavascripttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established SurveyJS package; provenance not historically provided across 335 versions. ai
provenance missing-githead AI (provenance): Publish environment change for a well-established package; no malicious signal. ai

Versions (showing 83 of 83)

Version Deps Published
2.5.35 0 / 0
2.5.34 0 / 0
2.5.33 0 / 0
2.5.32 0 / 0
2.5.31 0 / 0
2.5.30 0 / 0
2.5.29 0 / 0
2.5.28 0 / 0
2.5.27 0 / 0
2.5.26 0 / 0
2.5.25 0 / 0
2.5.24 0 / 0
2.5.23 0 / 0
2.5.22 0 / 0
2.5.21 0 / 0
2.5.20 0 / 0
2.5.19 0 / 0
2.5.18 0 / 0
2.5.17 0 / 0
2.5.16 0 / 0
2.5.15 0 / 0
2.5.14 0 / 0
2.5.13 0 / 0
2.5.12 0 / 0
2.5.11 0 / 0
2.5.10 0 / 0
2.5.9 0 / 0
2.5.8 0 / 0
2.5.7 0 / 0
2.5.6 0 / 0
2.5.5 0 / 0
2.5.4 0 / 0
2.5.3 0 / 0
2.5.2 0 / 0
2.5.1 0 / 0
2.5.0 0 / 0
2.4.1 0 / 0
2.4.0 0 / 0
2.3.16 0 / 0
2.3.15 0 / 0
2.3.14 0 / 0
2.3.13 0 / 0
2.3.12 0 / 0
2.3.11 0 / 0
2.3.10 0 / 0
2.3.9 0 / 0
2.3.8 0 / 0
2.3.7 0 / 0
2.3.6 0 / 0
2.3.5 0 / 0
2.3.4 0 / 0
2.3.3 0 / 0
2.3.2 0 / 0
2.3.1 0 / 0
2.3.0 0 / 0
2.2.6 0 / 0
2.2.5 0 / 0
2.2.4 0 / 0
2.2.3 0 / 0
2.2.2 0 / 0
2.2.1 0 / 0
2.2.0 0 / 0
2.1.1 0 / 0
2.1.0 0 / 0
2.0.10 0 / 0
2.0.9 0 / 0
2.0.8 0 / 0
2.0.7 0 / 0
2.0.6 0 / 0
2.0.5 0 / 0
2.0.4 0 / 0
2.0.3 0 / 0
2.0.2 0 / 0
2.0.1 0 / 0
2.0.0 0 / 0
1.12.64 0 / 0
1.12.63 0 / 0
1.12.62 0 / 0
1.12.61 0 / 0
1.12.60 0 / 0
1.12.59 0 / 0
1.12.58 0 / 0
1.12.57 0 / 0

v2.5.35

1 finding
INFO No provenance attestation provenance

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

v2.5.34

1 finding
INFO No provenance attestation provenance

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

v2.5.33

1 finding
INFO No provenance attestation provenance

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

v2.5.32

1 finding
INFO No provenance attestation provenance

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

v2.5.31

1 finding
INFO No provenance attestation provenance

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

v2.5.30

1 finding
INFO No provenance attestation provenance

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

v2.5.17

1 finding
INFO No provenance attestation provenance

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

v2.0.6

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.4

1 finding
INFO No provenance attestation provenance

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

v2.0.3

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

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

v1.12.64

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: duodvk.