survey-core
A framework-independent core of the SurveyJS Form Library that works with rendering packages. Use it to integrate dynamic, interactive JSON-based forms and surveys into your app, collect user responses, and send them to your own database.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build-env change only; no behavioral signal for this high-trust package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Bundled build output (CSS/maps); benign for this build-heavy library. | ai |
Versions (showing 44 of 44)
| 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.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 | |
| 1.12.64 | 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.64
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: duodvk.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.62
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: duodvk.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.