In fact it appears that swiftly makes a network connection every time you invoke swiftly run, which is a problem whenever WiFi is wonky or misconfigured on Linux (as happens!), because then it can hang for minutes at a time:
$ strace -f swiftly run echo 2>&1 | grep connect
[pid 121526] connect(79, {sa_family=AF_INET6, sin6_port=htons(65535), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2620:149:a33:f000::133", &sin6_addr), sin6_scope_id=0}, 28 <unfinished ...>
[pid 121526] <... connect resumed>) = 0
[pid 121526] connect(79, {sa_family=AF_INET6, sin6_port=htons(65535), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2620:149:a33:f000::148", &sin6_addr), sin6_scope_id=0}, 28 <unfinished ...>
[pid 121526] <... connect resumed>) = 0
[pid 121526] connect(79, {sa_family=AF_INET, sin_port=htons(65535), sin_addr=inet_addr("17.253.3.132")}, 16 <unfinished ...>
[pid 121526] <... connect resumed>) = 0
[pid 121526] connect(79, {sa_family=AF_INET, sin_port=htons(65535), sin_addr=inet_addr("17.253.3.145")}, 16) = 0
[pid 121498] getpeername(79, 0x7a6a2664de30, [128]) = -1 ENOTCONN (Transport endpoint is not connected)
[pid 121498] connect(79, {sa_family=AF_INET6, sin6_port=htons(443), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "2620:149:a33:f000::133", &sin6_addr), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
$ host 17.253.3.132
132.3.253.17.in-addr.arpa domain name pointer usnyc3-vip-fx-101.b.aaplimg.com.
$ host 17.253.3.145
145.3.253.17.in-addr.arpa domain name pointer usnyc3-vip-fx-108.a.aaplimg.com.
$ whois aaplimg.com | grep 'Name Server'
Name Server: A.NS.APPLE.COM
Name Server: B.NS.APPLE.COM
Name Server: C.NS.APPLE.COM
Name Server: D.NS.APPLE.COM
Name Server: a.ns.apple.com
Name Server: b.ns.apple.com
Name Server: c.ns.apple.com
Name Server: d.ns.apple.com
I think it would be better if swiftly only checked for self-updates when you ran a command which must make a network connection by design, like list-available or install.