sb-admin-2 template within production

Should I submit the template `/templates/sb-admin-2` to my source controller? If not how should stats panels going to work in production?
Git would not show up the 'public\templates\sb-admin-2\` folder to submit due to `public\templates\sb-admin-2\.git` .git folder should I delete it?
Currently in my local I can reach `/templates/sb-admin-2`. and if I submit in production the template will be reachable by anonymous user as well. How should I limit the access?

Start by inspecting the /templates/sb-admin-2 directory and its nested .git folder, then trace how the template is deployed and how the /templates/sb-admin-2 route is exposed in production. Done means determining whether the template and nested repository belong in source control and documenting or implementing how anonymous access should be restricted.

Written by the indexing model from the issue text.