Website

[nalinbhardwaj]

TODO: deploy from master CI

Closes #18

[socket-security[bot]]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
next	13.5.3	eval, network, filesystem, shell, environment	+28	1.11 GB	vercel-release-bot
@types/react-syntax-highlighter	15.5.7	None	+4	1.79 MB	types
eslint-config-next	13.5.3	eval, filesystem, environment	+174	23.3 MB	vercel-release-bot
postcss	8.4.31	environment	+3	372 kB	ai
@types/react-dom	18.2.8	None	+4	1.63 MB	types
react-hot-toast	2.4.1	environment	+7	6.44 MB	timolins
@types/react	18.2.24	None	+3	1.6 MB	types
autoprefixer	10.4.16	filesystem, shell, environment	+12	3.09 MB	ai
@types/node	20.8.0	None	+0	3.92 MB	types
react	18.2.0	environment	+2	337 kB	gnoff
react-syntax-highlighter	15.5.0	filesystem, environment	+27	10.1 MB	simmerer
react-dom	18.2.0	environment	+4	4.93 MB	gnoff
tailwindcss	3.3.3	filesystem, environment	+76	8.94 MB	adamwathan
eslint	8.50.0	eval, filesystem, environment	+94	10 MB	eslintbot

[socket-security[bot]]

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

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

Issue	Package	Version	Note	Source
Telemetry	next	13.5.3	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	website/package.json

Next steps

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore next@13.5.3