@dcl/ts-proto ISC 3 versions

@dcl/ts-proto

[![npm](https://img.shields.io/npm/v/ts-proto)](https://www.npmjs.com/package/ts-proto) [![build](https://github.com/stephenh/ts-proto/workflows/Build/badge.svg)](https://github.com/stephenh/ts-proto/actions)

Versions

ISC

License

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

decentralandbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:dataloader	AI (phantom-deps): Referenced in config files only; not a real import gap for this protobuf codegen tool.	ai	2026/04/29
phantom-deps	phantom-dep:object-hash	AI (phantom-deps): Referenced in config files only; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/object-hash	AI (phantom-deps): Type-definition package loaded by convention; not a real phantom-dep risk.	ai	2026/04/29

Versions (showing 3 of 3)

Version	Deps	Published
1.154.0	7 / 31	2023-07-31
1.153.0	7 / 31	2023-07-14
1.146.2	7 / 29	2023-05-10

v1.153.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.146.2

1 finding

LOW No provenance attestation provenance

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