You can vary the display name as it appears in the Add-ins window by editing the Title
Built-in Document Property, but that doesn't help you with the name in the References window
The VBE won't let you use illegal characters in a project name of module name, but that doesn't mean it can't be done.
For example, the Analysis Toolpak - VBA add-in ATPVBAEN.XLAM
has a project name of atpvbaen.xls
which includes the supposedly illegal character .
Likewise, the same project has a module called VBA Functions and Subs
which includes the illegal
(space) character.
But the public procedures in Analysis Toolpak are still callable by using square brackets.
Sub test()
'Run the auto_open macro in Analysis Toolpak
[atpvbaen.xls].[VBA Functions and Subs].auto_open
End Sub
So Microsoft knows how to use illegal characters in project and module names, which is presumably done in the binary or with a special build of VBE.
EDIT
I just edited the binary of a VBA project and was able to put spaces in the VBA project name!
Interestingly, you can't export and then reimport the modules from Analysis Toolpak, as VBE still enforces the naming rules on import. Good luck getting that to work with Source Control.
EDIT: 3 FEB 2017
From the VBA file format spec: [MS-OVBA]
[module name] SHOULD be an identifier... MAY be any string of characters... MUST be less than or equal to 31 characters long.
[project name] SHOULD be an identifier... MAY be any string of characters... MUST be less than or equal to 128 characters long.
So it seems the VBE is imposing the SHOULD rule, but VBA is actually more permissive, if you are able to edit the project binary.