You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In nuget -- and all repositories based on it, such as chocolatey and the PowerShell Gallery -- the "Author" is just metadata. There's no validation, and indeed in the early days, many PowerShell modules (and nuget packages) were created and uploaded by people who did not write the original code, just to get the module into the gallery where it would be available.
In fact, in the spirit of hacker ethos, these modules frequently go out of their way to make it easy for packagers to remain essentially unknown, featuring "contact" forms that are essentially anonymous. That's not totally unreasonable, but it's certainly unpopular these days.
Summary of the new feature / enhancement
In nuget -- and all repositories based on it, such as chocolatey and the PowerShell Gallery -- the "Author" is just metadata. There's no validation, and indeed in the early days, many PowerShell modules (and nuget packages) were created and uploaded by people who did not write the original code, just to get the module into the gallery where it would be available.
In fact, in the spirit of hacker ethos, these modules frequently go out of their way to make it easy for packagers to remain essentially unknown, featuring "contact" forms that are essentially anonymous. That's not totally unreasonable, but it's certainly unpopular these days.
On the PowerShell Gallery web interface, you need to search for a module to see the uploader. The uploader isn't visible on https://powershellgallery.com/packages/terminalblocks but only on https://powershellgallery.com/packages?q=terminalblocks ... -- however, if you click on the username, you can see all the modules uploaded by that same account!
Can we add the uploader to the module info page, with that same link to see all the modules uploaded by that account?
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: