Git authentication failure during bower install

Bower Dependency Resolution

Bower delegates authentication for private repositories to the underlying version control system, typically Git. When executing bower install, the tool triggers clone or pull operations based on the entries in bower.json.

Credential Expiration Constraints

Because Bower does not natively manage credentials or provide a built-in mechanism for token refresh, it relies entirely on the system's Git configuration or an active SSH agent. If the remote repository requires authentication and the stored credentials have expired or are missing, the process fails at the Git level.

Given this delegation model, what is the expected behavior when a partial installation occurs before an authentication failure is encountered? Does Bower maintain a corrupted state in the bower_components directory, or is the operation atomic across all dependencies?