Contract Explorer: Contract spec

[quietbits]

Note

PR preview doesn't properly render the code editor because of the CSP rules. You can test by running this branch locally.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	54 MB	nightwing
npm/[email protected]	None	0	97.4 kB	jackub
npm/[email protected]	None	0	26.5 kB	jdalton
npm/[email protected]	environment	0	98.8 MB	microsoft1es
npm/[email protected]	None	0	2.01 MB	securingsincity

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Obfuscated code	npm/[email protected]	Confidence: 0.95 Location: Package overview	yarn.lock	⚠︎
Obfuscated code	npm/[email protected]	Confidence: 0.95 Location: Package overview	yarn.lock	⚠︎
Obfuscated code	npm/[email protected]	Confidence: 0.95 Location: Package overview	yarn.lock	⚠︎
Obfuscated code	npm/[email protected]	Confidence: 0.95 Location: Package overview	yarn.lock	⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[stellar-jenkins]

Preview is available here:
http://laboratory-pr1251.previews.kube001.services.stellar-ops.com/