component-runtime icon indicating copy to clipboard operation
component-runtime copied to clipboard

Security Policy violation Repository Administrators

Open talend-allstar-instance[bot] opened this issue 2 years ago • 40 comments

This issue was automatically created by Allstar.

Security Policy Violation Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)


This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Policy is now in compliance. Closing issue.

Reopening issue. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Updating issue after ping interval. See its status below.


Users are not allowed to be administrators of this repository. Instead a team should be added as administrator.

To add a team as administrator From the main page of the repository, go to Settings -> Manage Access. (For more information, see https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories)

Policy is now in compliance. Closing issue.