Skip to content

Providing a Jupyter enterprise level Security Configuration for orgs to opt-in to #106

Open
@consideRatio

Description

@consideRatio

It is possible to create a Security Configuration in the Jupyter GitHub enterprise, that can be adopted within organizations.

However, only one such configuration can be adopted by repositories. Due to that, whatever we define ought to include as much as reasonable to be accepted by many orgs. In JupyterHub we are now piloting a "GitHub Recommended minus Code scanning with CodeQL" Security Configuration, after having piloted the "GitHub recommended" and being unhappy about CodeQL. JupyterHubs use of a Security Configuration is tracked in jupyterhub/team-compass#768.

I think for now we can wait, but that we should define a Security Configuration on the enterprise level, and ask that orgs consider opting in to it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions