# Core Infrastructure Initiative (CII) badge

**URL:** <https://discourse.slicer.org/t/core-infrastructure-initiative-cii-badge/810>\
**Category:** Development\
**Created:** [August 2, 2017, 7:42pm UTC](https://discourse.slicer.org/t/core-infrastructure-initiative-cii-badge/810 "2017-08-02T19:42:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 2, 2017, 7:42pm UTC](https://discourse.slicer.org/t/core-infrastructure-initiative-cii-badge/810/1 "2017-08-02T19:42:58Z")

</div>

Working on cleanup the Slicer openhub [https://www.openhub.net/p/slicer](https://www.openhub.net/p/slicer)

we ended up creating Core Infrastructure Initiative (CII) badge.

See [https://bestpractices.coreinfrastructure.org/projects/1162](https://bestpractices.coreinfrastructure.org/projects/1162)

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 3, 2017, 2:38am UTC](https://discourse.slicer.org/t/core-infrastructure-initiative-cii-badge/810/2 "2017-08-03T02:38:45Z")

</div>

JC, thank you for doing this, and for sharing the information about CII. I didn’t know about it, and it is a very interesting initiative indeed. It is nice that they organized all those items. But it does look like filling it out would require significant effort!

I just have few comments

> 3D Slicer software is distributed under a BSD-style open source license

We had a discussion about this before with @mhalle, @pieper, @rkikinis et al - the sentence above is somewhat misleading. The fact of a matter is that Slicer license is not a BSD license. There is no such thing as “BSD-style license”.

How about “3D Slicer software is distributed under a permissive open source license that permits academic and commercial reuse of the source code”, or something along those lines?

> [Issues · Slicer/Slicer · GitHub](https://issues.slicer.org/plugin.php?page=MantisGraph/status_graph.php)  
> [Issues · Slicer/Slicer · GitHub](https://issues.slicer.org/plugin.php?page=MantisGraph/issues_trend_graph.php)

These URLs are not accessible to me, even after logging into Mantis. It probably makes sense to only refer to the publicly available resources.

> It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality. - Met

We don’t test coverage routinely - do we have any evidence this is the case?

What do you think is the proper way to address security vulnerabilities, static/dynamic analysis?

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [September 2, 2020, 8:04am UTC](https://discourse.slicer.org/t/core-infrastructure-initiative-cii-badge/810/3 "2020-09-02T08:04:23Z")

</div>

Thanks for letting me know this, I have managed to make a badge for my extension too:

[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4239/badge)](https://bestpractices.coreinfrastructure.org/projects/4239)