microsoft
chore: Update package.json to include the repository
#minor
Hi there! This change adds the repository property to your package.json file(s). Having this available provides a number of benefits to security tooling. For example, it allows for greater trust by checking for signed commits, contributors to a release and validating history with the project. It also allows for comparison between the source code and the published artifact in order to detect attacks on authors during the publication process. We validate that we're making a PR against the correct repository by comparing the metadata for the published artifact on npmjs.com against the metadata in the package.json file in the repository. This change is provided by a team at Microsoft -- we're happy to answer any questions you may have. (Members of this team include @s-tuli, @iarna, @v-rr, @v-jiepeng, @v-zhzhou and @v-gjy). If you would prefer that we not make these sorts of PRs to projects you maintain, please just say. If you'd like to learn more about what we're doing here, we've prepared a document talking about both this project and some of our other activities around supply chain security here: microsoft/Secure-Supply-Chain This PR provides repository metadata for the following packages:
- @bfc/adaptive-flow
- @bfc/adaptive-form
- @bfc/client
- @bfc/electron-server
- @bfc/extension
- @bfc/extension-client
- @bfc/form-dialogs
- @bfc/integration-tests
- @bfc/intellisense
- @bfc/eslint-plugin-bfcomposer
- @bfc/ui-shared
- @bfc/server
- @bfc/server-workers
- @botframework-composer/test-utils
- @bfc/built-in-functions
- @bfc/intellisense-languageserver
- @bfc/lg-languageserver
- @bfc/lu-languageserver
- @botframework-composer/types
- @bfc/ui-plugin-composer
- @bfc/ui-plugin-cross-trained
- plugin-name
- @bfc/ui-plugin-lg
- @bfc/ui-plugin-luis
- @bfc/ui-plugin-orchestrator
- @bfc/ui-plugin-prompts
- @bfc/ui-plugin-dialog-schema-editor
- @bfc/ui-plugin-select-dialog
- @bfc/ui-plugin-select-skill-dialog
Description
Task Item
Screenshots
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
:x: v-jiepeng sign now
You have signed the CLA already but the status is still pending? Let us recheck it.
Coverage remained the same at 55.954% when pulling cbb47118c7fbb6850d7615657324b59c436c09fe on v-jiepeng:patch-1 into f5208f0a1a860e75df1da47b4af670e1fb483f05 on microsoft:main.
@v-jiepeng it doesn't look like you have signed the Microsoft Contributor License Agreement.
