tokio-retry

tokio-retry is used at run time in 243 crates (of which 58 optionally). It is a direct run-time dependency in 64 crates. It's used only as a dev dependency in 13 crates (of which 2 directly).

Number of dependers	tokio-retry version	Downloads/month
236	0.3.0	1.6M
12	0.2.0	160
8	0.1.1	170

Depender (with downloads and own rev deps)			tokio-retry version
17K		rs-nomad		^0.3
8.3K		statsig-rs		^0.3.0
6.4K	7	near-workspaces		^0.3
5.7K	1	ngrok		^0.3.0
5.5K	4	frame-remote-externalities		^0.3.0
4.4K	7	databend-client		^0.3
4.0K		espup		^0.3.0
1.1K	1	retrom-service		^0.3.0
1.0K		sunspec_rs		^0.3.0
3.4K		fhir-sdk	optional	^0.3.0
900		carbon-rpc-transaction-crawler-datasource		^0.3.0
500		tonlib-client		^0.3
320		unc-workspaces		^0.3
270	2	ockam_api		^0.3.0
240		ockam_command		^0.3
220		utility-workspaces		^0.3
210	1	wrangler		^0.3
180	1	function-compose-proc-macros		^0.3.0
130		tonlib		^0.3
120		spyglass-netrunner		^0.3
100		sulfite		^0.3.0
100	1	ply_jobs		^0.3
	5	workspaces		^0.3
		near-fetch		^0.3
		dwh		^0.3.0
	1	esthri		^0.3
	2	arpa-contract-client		^0.3
		arpa-node		^0.3
	5	interledger-settlement		^0.2.0
		metrics-exporter-influx		^0.3.0
		roux-stream		^0.3
	3	gadget-sdk		^0.3.0
		sf-rs		^0.3.0
		dirtgrabber		^0.3
	3	stack_test_epic_wallet_impls		^0.1
		bonsaimq		^0.3.0
		nix-index		^0.3.0
		lambda_web_adapter		^0.3
		git-iris		^0.3.0
	1	stack_test_epic_wallet_controller		^0.1
		blog-replay		^0.3
		rcopy		^0.3.0
		cdpay		^0.1
	18	aptos-network		^0.3.0
	4	aptos-telemetry		^0.3
		recon-link		^0.1.1
		iot_device_bridge		^0.3
		chaotic-tempest-testbed		^0.3
		interledger-settlement-engines		^0.2.0
		zuul		^0.3
		hi-push		^0.3.0
		nightly-async-nats		^0.3
		dlm		^0.3.0
		eth_event_stream		^0.3
		minecraft-rs		^0.3
		meilies-client		^0.2.0
		vertigo-cli		^0.3
		fn-macros		^0.3.0
		obc-salt		^0.3
		robust-tokio-modbus		^0.3.0
		yta-rs		^0.3.0
340	18	ockam_node	optional	^0.3.0
270	3	ockam_identity	optional	^0.3.0
250		function-compose	dev	^0.3.0
		miltr-server	dev	^0.3.0
	1	ilp-node	dev	^0.2.0