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
I am working on a product that distributes node and npm as a dependency for an application, which revealed that the 'term-size' MacOS binary is not signed. As 'term-size' is a dependency of npm (a transitive dependency inside boxen which is inside of update-notifier), it would be good for the distributed binary to be codesigned by the entity that makes the binary.
The current workaround is to codesign it ourselves.
Especially since hardened runtime is soon to be required for Mac applications, it would be nice for this to be signed instead of having to deal with signing it myself in all the various dep folders.
I am working on a product that distributes node and npm as a dependency for an application, which revealed that the 'term-size' MacOS binary is not signed. As 'term-size' is a dependency of npm (a transitive dependency inside boxen which is inside of update-notifier), it would be good for the distributed binary to be codesigned by the entity that makes the binary.
The current workaround is to codesign it ourselves.
IssueHunt Summary
rvagg has been rewarded.
Backers (Total: $40.00)
Submitted pull Requests
Tips
IssueHunt has been backed by the following sponsors. Become a sponsor
The text was updated successfully, but these errors were encountered: