Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize Sanity template #28

Closed
wants to merge 5 commits into from
Closed

Conversation

kenjonespizza
Copy link
Contributor

No description provided.

@kenjonespizza kenjonespizza requested a review from a team as a code owner December 17, 2024 01:08
Copy link

vercel bot commented Dec 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sanity-template-nuxt-clean ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 17, 2024 10:34pm
sanity-template-nuxt-clean-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 17, 2024 10:34pm

Copy link

socket-security bot commented Dec 17, 2024

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

Package New capabilities Transitives Size Publisher
npm/@nuxtjs/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +212 117 MB danielroe
npm/@sanity/[email protected] None 0 178 kB rexxars
npm/@sanity/[email protected] Transitive: environment, network +26 5.85 MB
npm/@sanity/[email protected] Transitive: environment +79 23.4 MB ash
npm/@types/[email protected] None +1 2.1 MB types
npm/@types/[email protected] None +2 1.69 MB types
npm/[email protected] environment, filesystem, shell +25 7.13 MB gustavohenke
npm/[email protected] environment, filesystem Transitive: eval, shell, unsafe +96 10.7 MB eslintbot
npm/[email protected] None 0 11.8 kB ash
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +684 432 MB danielroe
npm/[email protected] None +3 223 kB ai
npm/[email protected] environment, filesystem +2 347 kB ai
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +815 710 MB ash
npm/[email protected] environment Transitive: filesystem +15 3.77 MB probablyup
npm/[email protected] None 0 22.7 MB typescript-bot

🚮 Removed packages: npm/@nuxtjs/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Copy link

🚨 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 NoteSourceCI
License Policy Violation npm/[email protected]
  • License: CC-BY-4.0 - Not allowed by license policy (package/ThirdPartyNoticeText.txt)
  • License: W3C-20150513 - Not allowed by license policy (package/ThirdPartyNoticeText.txt)
⚠︎
License Policy Violation npm/[email protected]
  • License: CC-BY-4.0 - Not allowed by license policy (npm metadata, package/LICENSE, package/package.json)
⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

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

@kenjonespizza
Copy link
Contributor Author

Closing in favor of a new PR #30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant