@webstudio-is/trpc-interface
Webstudio TRPC Interface
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@webstudio-is/feature-flags | AI (dependencies): Same-org monorepo sibling dependency; stable pattern across webstudio-is packages. | ai | |
| phantom-deps | phantom-dep:@webstudio-is/feature-flags | AI (phantom-deps): Same-org sibling dep; declared in package.json, phantom-dep heuristic misfires on monorepo internals. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo interface package; sparse README and no keywords are expected for this type of package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.268.0 | 6 / 3 | |
| 0.267.0 | 6 / 3 | |
| 0.266.0 | 6 / 3 | |
| 0.265.0 | 7 / 3 | |
| 0.264.0 | 7 / 3 | |
| 0.262.0 | 7 / 3 | |
| 0.261.1 | 7 / 3 | |
| 0.261.0 | 7 / 3 | |
| 0.260.2 | 7 / 3 |
v0.268.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.267.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.266.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.262.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.