@progress/telerik-winforms-mcp
Model Context Protocol for Telerik UI for WinForms
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): gRPC runtime dep used via config/proto files; stable false positive for this MCP server package. | ai | |
| phantom-deps | phantom-dep:@grpc/proto-loader | AI (phantom-deps): Proto-loader runtime dep used via config files; stable false positive for this MCP server package. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): MCP SDK runtime dep referenced in config; stable false positive for this MCP server package. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-licensing | AI (phantom-deps): Same-org licensing dep; expected for Telerik/Progress packages, stable false positive. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 5 / 1 | |
| 1.4.3 | 5 / 1 | |
| 1.4.2 | 5 / 1 | |
| 1.4.1 | 5 / 1 | |
| 1.4.0 | 5 / 1 | |
| 1.3.4 | 5 / 1 | |
| 1.3.1 | 5 / 1 | |
| 1.3.0 | 5 / 1 | |
| 1.2.2 | 5 / 1 | |
| 1.2.1 | 5 / 1 | |
| 1.2.0 | 5 / 1 | |
| 1.1.6 | 4 / 1 | |
| 1.1.5 | 4 / 1 | |
| 1.1.4 | 4 / 1 | |
| 1.1.3 | 4 / 1 | |
| 1.1.2 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 4 / 1 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.