@webstudio-is/sdk
Webstudio project data schema
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in executeExpression() for evaluating data-binding expressions — documented SDK behavior, not arbitrary user code execution. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a JSON stringify proxy helper — standard JS pattern, not obfuscation. | ai |
Versions (showing 100 of 136)
| Version | Deps | Published |
|---|---|---|
| 0.282.1 | 13 / 7 | |
| 0.282.0 | 13 / 7 | |
| 0.281.0 | 13 / 7 | |
| 0.280.1 | 13 / 7 | |
| 0.280.0 | 13 / 7 | |
| 0.279.0 | 13 / 7 | |
| 0.278.0 | 13 / 7 | |
| 0.277.0 | 13 / 7 | |
| 0.276.1 | 13 / 7 | |
| 0.276.0 | 13 / 7 | |
| 0.275.0 | 13 / 5 | |
| 0.274.5 | 12 / 5 | |
| 0.274.4 | 12 / 5 | |
| 0.274.3 | 12 / 5 | |
| 0.274.2 | 12 / 5 | |
| 0.274.1 | 12 / 5 | |
| 0.274.0 | 12 / 5 | |
| 0.273.0 | 12 / 5 | |
| 0.272.0 | 12 / 5 | |
| 0.271.0 | 12 / 5 | |
| 0.270.0 | 12 / 5 | |
| 0.269.0 | 12 / 5 | |
| 0.268.0 | 12 / 5 | |
| 0.267.0 | 11 / 5 | |
| 0.266.0 | 11 / 5 | |
| 0.265.0 | 12 / 4 | |
| 0.264.0 | 11 / 5 | |
| 0.263.0 | 11 / 5 | |
| 0.262.1 | 11 / 5 | |
| 0.262.0 | 11 / 5 | |
| 0.261.1 | 11 / 5 | |
| 0.261.0 | 11 / 5 | |
| 0.260.2 | 11 / 5 | |
| 0.259.0 | 11 / 5 | |
| 0.258.0 | 11 / 5 | |
| 0.257.0 | 11 / 5 | |
| 0.255.0 | 11 / 5 | |
| 0.254.0 | 11 / 5 | |
| 0.253.0 | 11 / 5 | |
| 0.252.2 | 11 / 5 | |
| 0.252.1 | 11 / 5 | |
| 0.238.0 | 10 / 5 | |
| 0.237.0 | 10 / 5 | |
| 0.236.0 | 10 / 5 | |
| 0.235.0 | 10 / 5 | |
| 0.234.0 | 10 / 5 | |
| 0.233.0 | 10 / 5 | |
| 0.232.0 | 10 / 5 | |
| 0.208.0 | 9 / 5 | |
| 0.207.0 | 9 / 5 | |
| 0.206.0 | 9 / 5 | |
| 0.205.0 | 9 / 5 | |
| 0.204.0 | 8 / 5 | |
| 0.203.0 | 8 / 5 | |
| 0.202.0 | 8 / 5 | |
| 0.201.0 | 8 / 5 | |
| 0.200.0 | 8 / 5 | |
| 0.199.0 | 8 / 5 | |
| 0.198.0 | 7 / 5 | |
| 0.197.0 | 7 / 5 | |
| 0.196.0 | 7 / 6 | |
| 0.195.0 | 7 / 6 | |
| 0.194.0 | 7 / 5 | |
| 0.193.0 | 7 / 5 | |
| 0.192.0 | 7 / 5 | |
| 0.191.5 | 7 / 5 | |
| 0.191.4 | 7 / 5 | |
| 0.191.0 | 7 / 5 | |
| 0.189.0 | 7 / 6 | |
| 0.185.0 | 7 / 6 | |
| 0.182.0 | 6 / 6 | |
| 0.181.0 | 6 / 6 | |
| 0.179.0 | 6 / 6 | |
| 0.175.0 | 6 / 6 | |
| 0.174.0 | 6 / 4 | |
| 0.173.0 | 6 / 4 | |
| 0.168.0 | 6 / 4 | |
| 0.167.0 | 6 / 4 | |
| 0.163.0 | 6 / 4 | |
| 0.151.0 | 6 / 4 | |
| 0.145.0 | 6 / 4 | |
| 0.144.0 | 5 / 3 | |
| 0.143.1 | 5 / 3 | |
| 0.143.0 | 5 / 3 | |
| 0.142.0 | 3 / 3 | |
| 0.141.0 | 3 / 3 | |
| 0.140.0 | 3 / 3 | |
| 0.139.0 | 3 / 3 | |
| 0.138.0 | 3 / 3 | |
| 0.137.0 | 3 / 3 | |
| 0.136.0 | 3 / 3 | |
| 0.135.0 | 3 / 3 | |
| 0.134.0 | 3 / 3 | |
| 0.133.0 | 3 / 3 | |
| 0.132.0 | 3 / 3 | |
| 0.131.0 | 3 / 3 | |
| 0.130.0 | 3 / 3 | |
| 0.129.0 | 3 / 3 | |
| 0.128.0 | 3 / 3 | |
| 0.127.0 | 3 / 3 |
v0.282.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.282.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.281.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.280.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.280.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.279.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.278.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.277.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.276.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.276.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.275.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.273.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.258.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.257.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.255.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.254.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.253.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.252.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.252.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.238.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.237.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.236.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (trysound) than the most recent previously approved version (kof) on 2025-12-05, but trysound is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.235.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.234.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.233.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.232.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.208.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.207.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.206.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.205.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.204.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.203.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.202.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.201.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.200.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.199.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.198.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.197.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.196.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.195.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.194.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.193.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.192.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.191.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.191.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.191.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.189.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.185.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.182.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.181.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.179.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.175.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.174.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.173.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.168.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.167.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.151.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.145.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.144.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.143.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.143.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.142.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.141.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.140.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.139.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.138.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.137.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.136.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.135.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.134.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.133.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.132.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.131.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.130.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.129.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.127.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.