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
Hey there, Carbon team member here! 👋 We'd like to ensure the security practices for packages published from the carbon-design-system GitHub org are in place and up to date. We'd like to work with you to get the following security practices implemented:
The content you are editing has changed. Please copy your edits and refresh the page.
Most of these can be found under the Security tab for this repository. You may already have most of these implemented and turned on - if so, awesome!
For establishing a security policy, the existing security policy for the Carbon monorepo can be used as a template if you'd like. It can be modified to include proper version(s) for your package and any other attributes unique to your project that you may want to highlight.
I'm happy to meet up and chat about this if you'd like, just let me know. Thanks in advance for your help in ensuring security and stability across the Carbon ecosystem! 🙏 💙
The text was updated successfully, but these errors were encountered:
All items are added. However, provenance is not yet published. Currently Github Actions has some issues (see #150 ).
The other items are complete and I have gone ahead and set the package.json file to provenance; so need to run from GitHub actions to have the standard approach npm ERR! Automatic provenance generation not supported outside of GitHub Actions
@tay1orjones if you have some time could you help me with the GitHub action issue #150?
Hey there, Carbon team member here! 👋 We'd like to ensure the security practices for packages published from the
carbon-design-system
GitHub org are in place and up to date. We'd like to work with you to get the following security practices implemented:Tasks
Most of these can be found under the Security tab for this repository. You may already have most of these implemented and turned on - if so, awesome!
For establishing a security policy, the existing security policy for the Carbon monorepo can be used as a template if you'd like. It can be modified to include proper version(s) for your package and any other attributes unique to your project that you may want to highlight.
I'm happy to meet up and chat about this if you'd like, just let me know. Thanks in advance for your help in ensuring security and stability across the Carbon ecosystem! 🙏 💙
The text was updated successfully, but these errors were encountered: