etcd3
Node client for etcd3
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Regenerated protobuf compiled output via build:proto, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size jump matches generated rpc-compiled.js/proto artifacts. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-established library in maintenance mode; dormancy expected. | ai | |
| dependencies | unvetted-dep:cockatiel | AI (dependencies): cockatiel is a legitimate, well-known resilience library; its use in an etcd client for retry/circuit-breaker logic is expected and appropriate. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 4 / 30 | |
| 1.1.1 | 4 / 30 | |
| 1.1.0 | 4 / 29 | |
| 1.0.2 | 4 / 27 | |
| 1.0.1 | 4 / 27 | |
| 1.0.0 | 4 / 27 |
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.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.