@dcl/rpc
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @dcl/rpc is Decentraland's RPC library, not a typosquat of pg; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:ts-proto | AI (phantom-deps): ts-proto is a runtime dependency used for protobuf codegen; phantom-dep heuristic fires but it's legitimately declared. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 2 / 12 | |
| 1.1.1 | 2 / 12 | |
| 1.1.0 | 2 / 12 | |
| 1.0.3 | 3 / 12 | |
| 1.0.2 | 3 / 12 | |
| 1.0.1 | 3 / 12 | |
| 1.0.0 | 3 / 12 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.