| 0 |
AK |
http://dhss.alaska.gov/dph/Epi/id/Pages/COVID-19/monitoring.aspx |
http://dhss.alaska.gov/dph/Epi/id/Pages/COVID-19/default.aspx |
@Alaska_DHSS |
All data |
False |
Unclear if their reported number means "persons tested" or "specimens tested." We count them as "persons tested" because the header indicates this is the case. Negatives reported on site have decreased at various times in recent hours, without explanation. |
Alaska |
AK |
http://dhss.alaska.gov/dph/Epi/id/Pages/COVID-19/default.aspx |
http://dhss.alaska.gov/dph/Epi/id/Pages/COVID-19/monitoring.aspx |
google-states |
| 1 |
AL |
http://www.alabamapublichealth.gov/infectiousdiseases/2019-coronavirus.html |
http://www.alabamapublichealth.gov/infectiousdiseases/2019-coronavirus.html |
@alpublichealth |
No data |
False |
Last negative count from 3/16. |
Alabama |
AL |
http://www.alabamapublichealth.gov/infectiousdiseases/2019-coronavirus.html |
http://www.alabamapublichealth.gov/infectiousdiseases/2019-coronavirus.html |
google-states |
| 2 |
AR |
https://www.healthy.arkansas.gov/programs-services/topics/novel-coronavirus |
https://www.healthy.arkansas.gov/programs-services/topics/novel-coronavirus |
@adhpio |
All data |
True |
Pending = "PUIs" |
Arkansas |
AR |
https://www.healthy.arkansas.gov/programs-services/topics/novel-coronavirus |
https://www.healthy.arkansas.gov/programs-services/topics/novel-coronavirus |
google-states |
| 3 |
AZ |
https://www.azdhs.gov/preparedness/epidemiology-disease-control/infectious-disease-epidemiology/index.php#novel-coronavirus-home |
https://www.azdhs.gov/preparedness/epidemiology-disease-control/infectious-disease-epidemiology/index.php#novel-coronavirus-home |
@azdhs |
All data |
False |
Negative = “Ruled Out”. Our total is slightly higher than the state’s site because their total is only from public health labs. We also add in the additional positives from private labs, listed in the second table. |
Arizona |
AZ |
https://www.azdhs.gov/preparedness/epidemiology-disease-control/infectious-disease-epidemiology/index.php#novel-coronavirus-home |
https://www.azdhs.gov/preparedness/epidemiology-disease-control/infectious-disease-epidemiology/index.php#novel-coronavirus-home |
google-states |
| 4 |
CA |
https://www.latimes.com/projects/california-coronavirus-cases-tracking-outbreak/ |
https://www.cdph.ca.gov/Programs/CID/DCDC/Pages/Immunization/ncov2019.aspx |
@CAPublicHealth |
Only positives |
False |
Only positives reported regularly. Add deaths to the positive count. Last negative inferred from 3/18 Newsom [press conference](https://www.facebook.com/CAgovernor/videos/540366033561809/). In addition, we will be ignoring irregularly reported pending numbers when they come from a non-dashboard source. |
California |
CA |
https://www.cdph.ca.gov/Programs/CID/DCDC/Pages/Immunization/ncov2019.aspx |
https://www.latimes.com/projects/california-coronavirus-cases-tracking-outbreak/ |
google-states |
| 5 |
CO |
https://covid19.colorado.gov/data |
https://www.colorado.gov/pacific/cdphe/2019-novel-coronavirus |
@cdphe |
Positives + Negatives |
False |
Negative is from state lab only. Total private tests unknown. Death count from [media](https://kdvr.com/news/coronavirus/colorados-second-coronavirus-death-reported-in-weld-county/). Changed data site 3/17. Now only report positive. Total tests from [media](https://kdvr.com/news/coronavirus/new-website-tracks-coronavirus-cases-in-colorado-statewide-total-now-at-183/). |
Colorado |
CO |
https://www.colorado.gov/pacific/cdphe/2019-novel-coronavirus |
https://covid19.colorado.gov/data |
google-states |
| 6 |
CT |
https://portal.ct.gov/Coronavirus |
https://portal.ct.gov/Coronavirus |
@ctdph |
All data |
False |
Last negative count from 3/13 |
Connecticut |
CT |
https://portal.ct.gov/Coronavirus |
https://portal.ct.gov/Coronavirus |
google-states |
| 7 |
DC |
https://coronavirus.dc.gov/page/coronavirus-surveillance-data |
https://coronavirus.dc.gov/ |
@_DCHealth |
All data |
False |
Adding all positives together. Negative count dropped 3/11, back 3/13 |
District Of Columbia |
DC |
https://coronavirus.dc.gov/ |
https://coronavirus.dc.gov/page/coronavirus-surveillance-data |
google-states |
| 8 |
DE |
https://dhss.delaware.gov/dhss/dph/epi/2019novelcoronavirus.html |
https://dhss.delaware.gov/dhss/dph/epi/2019novelcoronavirus.html |
@Delaware_DHSS |
All data |
True |
Last reported negative number is from 3/13. |
Delaware |
DE |
https://dhss.delaware.gov/dhss/dph/epi/2019novelcoronavirus.html |
https://dhss.delaware.gov/dhss/dph/epi/2019novelcoronavirus.html |
google-states |
| 9 |
FL |
https://experience.arcgis.com/experience/96dd742462124fa0b38ddedb9b25e429/ |
http://www.floridahealth.gov/diseases-and-conditions/COVID-19/ |
@HealthyFla |
All data |
True |
Deaths from [press release](Deaths from press release: http://www.floridahealth.gov/newsroom/2020/03/031920-1127-covid19.pr.html) |
Florida |
FL |
http://www.floridahealth.gov/diseases-and-conditions/COVID-19/ |
https://experience.arcgis.com/experience/96dd742462124fa0b38ddedb9b25e429/ |
google-states |
| 10 |
GA |
https://dph.georgia.gov/georgia-department-public-health-covid-19-daily-status-report |
https://dph.georgia.gov/novelcoronavirus |
@GaDPH |
Only positives |
False |
Positive includes deaths. The page includes a "report generated" time at the bottom of the page and a data "as of" time. We use the "as of" time a the top of the page as our Update Time. |
Georgia |
GA |
https://dph.georgia.gov/novelcoronavirus |
https://dph.georgia.gov/georgia-department-public-health-covid-19-daily-status-report |
google-states |
| 11 |
HI |
https://hawaiicovid19.com/ |
https://health.hawaii.gov/docd/advisories/novel-coronavirus-2019/ |
@HIgov_Health |
Only positives |
False |
Now reporting negatives in daily [press releases](https://health.hawaii.gov/news/covid-19-updates/). |
Hawaii |
HI |
https://health.hawaii.gov/docd/advisories/novel-coronavirus-2019/ |
https://hawaiicovid19.com/ |
google-states |
| 12 |
IA |
https://idph.iowa.gov/Emerging-Health-Issues/Novel-Coronavirus |
https://idph.iowa.gov/Emerging-Health-Issues/Novel-Coronavirus |
@IAPublicHealth |
All data |
False |
Last negative from 3/12. Use time = 00:00 |
Iowa |
IA |
https://idph.iowa.gov/Emerging-Health-Issues/Novel-Coronavirus |
https://idph.iowa.gov/Emerging-Health-Issues/Novel-Coronavirus |
google-states |
| 13 |
ID |
https://coronavirus.idaho.gov/ |
https://coronavirus.idaho.gov/ |
@IDHW |
All data |
True |
Total includes Oregon residents tested in Idaho, as the state does in its table (noted below). Negative = total tests - confirmed positives. |
Idaho |
ID |
https://coronavirus.idaho.gov/ |
https://coronavirus.idaho.gov/ |
google-states |
| 14 |
IL |
http://www.dph.illinois.gov/topics-services/diseases-and-conditions/diseases-a-z-list/coronavirus |
http://www.dph.illinois.gov/topics-services/diseases-and-conditions/diseases-a-z-list/coronavirus |
@IDPH |
All data |
False |
Our data differs from Illinois because we count deaths as positives. |
Illinois |
IL |
http://www.dph.illinois.gov/topics-services/diseases-and-conditions/diseases-a-z-list/coronavirus |
http://www.dph.illinois.gov/topics-services/diseases-and-conditions/diseases-a-z-list/coronavirus |
google-states |
| 15 |
IN |
https://www.in.gov/isdh/28470.htm |
https://www.in.gov/isdh/28470.htm |
@statehealthin |
Only positives |
False |
Negative count is a lower bound: we subtract total lab positives from IDPH/CDC totals. |
Indiana |
IN |
https://www.in.gov/isdh/28470.htm |
https://www.in.gov/isdh/28470.htm |
google-states |
| 16 |
KS |
http://www.kdheks.gov/coronavirus/ |
http://www.kdheks.gov/coronavirus/ |
@kdhe |
All data |
False |
Death from [article](https://www.cjonline.com/news/20200316/kelly-imposes-cdc-limit-of-50-people-at-gatherings-kansas-documents-11-cases) |
Kansas |
KS |
http://www.kdheks.gov/coronavirus/ |
http://www.kdheks.gov/coronavirus/ |
google-states |
| 17 |
KY |
https://chfs.ky.gov/agencies/dph/Pages/covid19.aspx |
https://chfs.ky.gov/agencies/dph/Pages/covid19.aspx |
@CHFSKy |
All data |
False |
Death from [news reports](https://www.wdrb.com/news/coronavirus/kentucky-governor-confirms-state-s-first-coronavirus-related-death/article_bde65e98-66e9-11ea-b91c-2b91947df1b8.html). |
Kentucky |
KY |
https://chfs.ky.gov/agencies/dph/Pages/covid19.aspx |
https://chfs.ky.gov/agencies/dph/Pages/covid19.aspx |
google-states |
| 18 |
LA |
http://ldh.la.gov/Coronavirus/ |
http://ldh.la.gov/Coronavirus/ |
@LADeptHealth |
Only positives |
False |
New press release only includes positive numbers. Negative = Total - Positive. Totals only provided for public health lab, so negatives are a lower bound. |
Louisiana |
LA |
http://ldh.la.gov/Coronavirus/ |
http://ldh.la.gov/Coronavirus/ |
google-states |
| 19 |
MA |
https://www.mass.gov/info-details/covid-19-cases-quarantine-and-monitoring |
https://www.mass.gov/resource/information-on-the-outbreak-of-coronavirus-disease-2019-covid-19 |
@massdph |
Only positives |
True |
Positives include 8 CDC tests as noted in the PDF. Negatives calculated from the PDF. Updates at 4pm. |
Massachusetts |
MA |
https://www.mass.gov/resource/information-on-the-outbreak-of-coronavirus-disease-2019-covid-19 |
https://www.mass.gov/info-details/covid-19-cases-quarantine-and-monitoring |
google-states |
| 20 |
MD |
https://phpa.health.maryland.gov/Pages/Novel-coronavirus.aspx |
https://phpa.health.maryland.gov/Pages/Novel-coronavirus.aspx |
@MDHealthDept |
All data |
False |
Last negative on 3/12. Use time = 10:00. Deaths now reported on website. |
Maryland |
MD |
https://phpa.health.maryland.gov/Pages/Novel-coronavirus.aspx |
https://phpa.health.maryland.gov/Pages/Novel-coronavirus.aspx |
google-states |
| 21 |
ME |
https://www.maine.gov/dhhs/mecdc/infectious-disease/epi/airborne/coronavirus.shtml |
https://www.maine.gov/dhhs/mecdc/infectious-disease/epi/airborne/coronavirus.shtml |
@mainedhhs |
Only positives |
False |
Use the time at the top row of the table. Recovered added to Positive to count accurately towards total. |
Maine |
ME |
https://www.maine.gov/dhhs/mecdc/infectious-disease/epi/airborne/coronavirus.shtml |
https://www.maine.gov/dhhs/mecdc/infectious-disease/epi/airborne/coronavirus.shtml |
google-states |
| 22 |
MI |
https://www.michigan.gov/coronavirus/0,9753,7-406-98163-520743--,00.html |
https://www.michigan.gov/coronavirus |
@MichiganHHS |
All data |
True |
Positive count only, as of 3/16. Negative count is last reported value as of 3/16. |
Michigan |
MI |
https://www.michigan.gov/coronavirus |
https://www.michigan.gov/coronavirus/0,9753,7-406-98163-520743--,00.html |
google-states |
| 23 |
MN |
https://www.health.state.mn.us/diseases/coronavirus/situation.html |
https://www.health.state.mn.us/diseases/coronavirus/index.html |
@mnhealth |
All data |
False |
Negative = Total - Positive. Totals only provided for public health lab, so negatives are a lower bound. |
Minnesota |
MN |
https://www.health.state.mn.us/diseases/coronavirus/index.html |
https://www.health.state.mn.us/diseases/coronavirus/situation.html |
google-states |
| 24 |
MO |
https://health.mo.gov/living/healthcondiseases/communicable/novel-coronavirus/ |
https://health.mo.gov/living/healthcondiseases/communicable/novel-coronavirus/ |
@HealthyLivingMo |
Only positives |
False |
NaN |
Missouri |
MO |
https://health.mo.gov/living/healthcondiseases/communicable/novel-coronavirus/ |
https://health.mo.gov/living/healthcondiseases/communicable/novel-coronavirus/ |
google-states |
| 25 |
MS |
https://msdh.ms.gov/msdhsite/_static/14,0,420.html |
https://msdh.ms.gov/msdhsite/_static/14,0,420.html |
@msdh |
Only positives |
False |
Negatives are calculated from total positives and state lab totals (Total - Positive). |
Mississippi |
MS |
https://msdh.ms.gov/msdhsite/_static/14,0,420.html |
https://msdh.ms.gov/msdhsite/_static/14,0,420.html |
google-states |
| 26 |
MT |
https://dphhs.mt.gov/publichealth/cdepi/diseases/coronavirusmt |
https://dphhs.mt.gov/publichealth/cdepi/diseases/coronavirusmt |
@dphhsmt |
All data |
True |
Use time = 19:00 on the previous weekday. We do not count a "part time resident" who has not had contacts in MT and wasn't tested there. |
Montana |
MT |
https://dphhs.mt.gov/publichealth/cdepi/diseases/coronavirusmt |
https://dphhs.mt.gov/publichealth/cdepi/diseases/coronavirusmt |
google-states |
| 27 |
NC |
https://www.ncdhhs.gov/covid-19-case-count-north-carolina |
https://www.ncdhhs.gov/divisions/public-health/coronavirus-disease-2019-covid-19-response-north-carolina |
@ncdhhs |
Only positives |
False |
Providing positives from state. Negative count from [3/14 news article](https://www.newsobserver.com/news/local/article241192746.html) including both state and private testing. |
North Carolina |
NC |
https://www.ncdhhs.gov/divisions/public-health/coronavirus-disease-2019-covid-19-response-north-carolina |
https://www.ncdhhs.gov/covid-19-case-count-north-carolina |
google-states |
| 28 |
ND |
https://www.health.nd.gov/diseases-conditions/coronavirus/north-dakota-coronavirus-cases |
https://www.health.nd.gov/diseases-conditions/coronavirus |
@NDDOH |
All data |
True |
Use time = 00:00 |
North Dakota |
ND |
https://www.health.nd.gov/diseases-conditions/coronavirus |
https://www.health.nd.gov/diseases-conditions/coronavirus/north-dakota-coronavirus-cases |
google-states |
| 29 |
NE |
http://dhhs.ne.gov/Pages/Coronavirus.aspx |
http://dhhs.ne.gov/Pages/Coronavirus.aspx |
@NEDHHS |
All data |
False |
Use time = 00:00 |
Nebraska |
NE |
http://dhhs.ne.gov/Pages/Coronavirus.aspx |
http://dhhs.ne.gov/Pages/Coronavirus.aspx |
google-states |
| 30 |
NH |
https://www.dhhs.nh.gov/dphs/cdcs/2019-ncov.htm |
https://www.dhhs.nh.gov/dphs/cdcs/2019-ncov.htm |
@NHPubHealth |
All data |
False |
Negative = Persons Tested at PHL – Persons with COVID-19 – Persons with Test Pending in PHL |
New Hampshire |
NH |
https://www.dhhs.nh.gov/dphs/cdcs/2019-ncov.htm |
https://www.dhhs.nh.gov/dphs/cdcs/2019-ncov.htm |
google-states |
| 31 |
NJ |
https://www.nj.gov/health/ |
https://www.nj.gov/health/cd/topics/ncov.shtml |
@NJDeptofHealth |
All data |
False |
Pending = PUI. Positive count includes deaths. Negatives + pending from State Lab only. State may be changing how it reports negatives: there was a drop in negative count on 3/16. \nData is in a table in the Spotlight section. |
New Jersey |
NJ |
https://www.nj.gov/health/cd/topics/ncov.shtml |
https://www.nj.gov/health/ |
google-states |
| 32 |
NM |
https://cv.nmhealth.org/ |
https://cv.nmhealth.org/ |
@NMDOH |
All data |
False |
NaN |
New Mexico |
NM |
https://cv.nmhealth.org/ |
https://cv.nmhealth.org/ |
google-states |
| 33 |
NV |
https://nvhealthresponse.nv.gov/ |
http://dpbh.nv.gov/coronavirus/ |
@dhhsnevada |
All data |
False |
Very rare updates. We rely on the Nevada Independent: [Live Blog](https://thenevadaindependent.com/article/coronavirus-live-blog-week-two) more than the [state webpage](http://dpbh.nv.gov/coronavirus/) |
Nevada |
NV |
http://dpbh.nv.gov/coronavirus/ |
https://nvhealthresponse.nv.gov/ |
google-states |
| 34 |
NY |
https://coronavirus.health.ny.gov/county-county-breakdown-positive-cases |
https://www.health.ny.gov/diseases/communicable/coronavirus/ |
@healthnygov |
Only positives |
False |
Positives from state site. Totals and (inferred) negatives from [press conference](https://www.governor.ny.gov). Deaths from [NY Daily News article](https://nymag.com/intelligencer/2020/03/new-york-coronavirus-cases-updates.html) |
New York |
NY |
https://www.health.ny.gov/diseases/communicable/coronavirus/ |
https://coronavirus.health.ny.gov/county-county-breakdown-positive-cases |
google-states |
| 35 |
OH |
https://coronavirus.ohio.gov/wps/portal/gov/covid-19/ |
https://odh.ohio.gov/wps/portal/gov/odh/know-our-programs/Novel-Coronavirus/welcome/ |
@OHdeptofhealth |
All data |
False |
Pending = "Persons Under Investigation." Carrying over negative count. |
Ohio |
OH |
https://odh.ohio.gov/wps/portal/gov/odh/know-our-programs/Novel-Coronavirus/welcome/ |
https://coronavirus.ohio.gov/wps/portal/gov/covid-19/ |
google-states |
| 36 |
OK |
https://coronavirus.health.ok.gov/ |
https://coronavirus.health.ok.gov |
@HealthyOklahoma |
All data |
False |
Pending = "PUIs pending results." Excluding "Positive (Out-of-State)." |
Oklahoma |
OK |
https://coronavirus.health.ok.gov |
https://coronavirus.health.ok.gov/ |
google-states |
| 37 |
OR |
https://www.oregon.gov/oha/PH/DISEASESCONDITIONS/DISEASESAZ/Pages/emerging-respiratory-infections.aspx |
https://www.oregon.gov/oha/PH/DISEASESCONDITIONS/DISEASESAZ/Pages/emerging-respiratory-infections.aspx |
@OHAOregon |
All data |
True |
Click to expand the Situation in Oregon section. Death sourced from [press release](https://www.oregon.gov/oha/ERD/Pages/State-Local-Officials-Announce-First-Fatality-from-COVID-19-in-Oregon.aspx\n). |
Oregon |
OR |
https://www.oregon.gov/oha/PH/DISEASESCONDITIONS/DISEASESAZ/Pages/emerging-respiratory-infections.aspx |
https://www.oregon.gov/oha/PH/DISEASESCONDITIONS/DISEASESAZ/Pages/emerging-respiratory-infections.aspx |
google-states |
| 38 |
PA |
https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx |
https://www.health.pa.gov/topics/disease/Pages/Coronavirus.aspx |
@PAHealthDept |
Only positives |
False |
County level data doesn't add up to the totals provided. We don't add deaths back into positives until we have more clarity on whether they are already included in the positive count. |
Pennsylvania |
PA |
https://www.health.pa.gov/topics/disease/Pages/Coronavirus.aspx |
https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx |
google-states |
| 39 |
RI |
https://health.ri.gov/data/covid-19/ |
https://health.ri.gov/diseases/respiratory/?parm=163 |
@rihealth |
All data |
False |
Use time = 00:00 |
Rhode Island |
RI |
https://health.ri.gov/diseases/respiratory/?parm=163 |
https://health.ri.gov/data/covid-19/ |
google-states |
| 40 |
SC |
https://scdhec.gov/health/infectious-diseases/viruses/coronavirus-disease-2019-covid-19/monitoring-testing-covid-19 |
https://scdhec.gov/health/infectious-diseases/viruses/coronavirus-disease-2019-covid-19 |
@scdhec |
All data |
True |
Positive = “Positive” + “Presumptive Positive”. \nDeaths from [a press release](https://www.scdhec.gov/news-releases/state-south-carolina-reports-first-covid-19-related-death). |
South Carolina |
SC |
https://scdhec.gov/health/infectious-diseases/viruses/coronavirus-disease-2019-covid-19 |
https://scdhec.gov/health/infectious-diseases/viruses/coronavirus-disease-2019-covid-19/monitoring-testing-covid-19 |
google-states |
| 41 |
SD |
https://doh.sd.gov/news/Coronavirus.aspx |
https://doh.sd.gov/news/Coronavirus.aspx |
@SDDOH |
All data |
False |
Use time = 00:00 |
South Dakota |
SD |
https://doh.sd.gov/news/Coronavirus.aspx |
https://doh.sd.gov/news/Coronavirus.aspx |
google-states |
| 42 |
TN |
https://www.tn.gov/health/cedep/ncov.html |
https://www.tn.gov/health/cedep/ncov.html |
@TNDeptofHealth |
Only positives |
False |
Negative count from state lab only, which reported 24/98 total positives. Use time = 15:00. |
Tennessee |
TN |
https://www.tn.gov/health/cedep/ncov.html |
https://www.tn.gov/health/cedep/ncov.html |
google-states |
| 43 |
TX |
https://dshs.texas.gov/news/updates.shtm#coronavirus |
https://dshs.texas.gov/coronavirus/ |
@TexasDSHS |
Only positives |
False |
Only positive counts. Use time = 13:00, as per the site's guidance.. |
Texas |
TX |
https://dshs.texas.gov/coronavirus/ |
https://dshs.texas.gov/news/updates.shtm#coronavirus |
google-states |
| 44 |
UT |
https://coronavirus-dashboard.utah.gov/ |
https://health.utah.gov/coronavirus |
@utahdepofhealth |
Only positives |
False |
Positives include non-Utah residents. Negative = Total - Positive. Totals are incomplete for private labs, so negatives are a lower bound. |
Utah |
UT |
https://health.utah.gov/coronavirus |
https://coronavirus-dashboard.utah.gov/ |
google-states |
| 45 |
VA |
https://public.tableau.com/views/VirginiaCOVID-19Dashboard/VirginiaCOVID-19Dashboard?:embed=yes&:display_count=yes&:showVizHome=no&:toolbar=no |
http://www.vdh.virginia.gov/surveillance-and-investigation/novel-coronavirus/ |
@vdhgov |
Positives + Negatives |
True |
Death sourced from [WAVY](https://www.wavy.com/news/health/coronavirus/gov-northam-to-addresses-coronavirus-concerns-as-vdh-confirms-41-cases-1-death/)\nUse time = 12:00 |
Virginia |
VA |
http://www.vdh.virginia.gov/surveillance-and-investigation/novel-coronavirus/ |
https://public.tableau.com/views/VirginiaCOVID-19Dashboard/VirginiaCOVID-19Dashboard?:embed=yes&:display_count=yes&:showVizHome=no&:toolbar=no |
google-states |
| 46 |
VT |
https://www.healthvermont.gov/response/infectious-disease/2019-novel-coronavirus |
https://www.healthvermont.gov/response/infectious-disease/2019-novel-coronavirus |
@healthvermont |
Positives + Negatives |
True |
Use time = 13:00. |
Vermont |
VT |
https://www.healthvermont.gov/response/infectious-disease/2019-novel-coronavirus |
https://www.healthvermont.gov/response/infectious-disease/2019-novel-coronavirus |
google-states |
| 47 |
WA |
https://www.doh.wa.gov/Emergencies/Coronavirus |
https://www.doh.wa.gov/Emergencies/Coronavirus |
@WADeptHealth |
Positives + Negatives |
True |
Total tests are below the tables with positive cases. Positive includes deaths. |
Washington |
WA |
https://www.doh.wa.gov/Emergencies/Coronavirus |
https://www.doh.wa.gov/Emergencies/Coronavirus |
google-states |
| 48 |
WI |
https://www.dhs.wisconsin.gov/outbreaks/index.htm |
https://www.dhs.wisconsin.gov/disease/covid-19.htm |
@DHSWI |
All data |
False |
No pending counts. Positive = “Positive” + “Positive Recovered” |
Wisconsin |
WI |
https://www.dhs.wisconsin.gov/disease/covid-19.htm |
https://www.dhs.wisconsin.gov/outbreaks/index.htm |
google-states |
| 49 |
WV |
https://dhhr.wv.gov/Coronavirus%20Disease-COVID-19/Pages/default.aspx |
https://dhhr.wv.gov/Coronavirus%20Disease-COVID-19/Pages/default.aspx |
@WV_DHHR |
All data |
False |
Pending = "Under Investigation". Data is in text. Use time = 00:00 |
West Virginia |
WV |
https://dhhr.wv.gov/Coronavirus%20Disease-COVID-19/Pages/default.aspx |
https://dhhr.wv.gov/Coronavirus%20Disease-COVID-19/Pages/default.aspx |
google-states |
| 50 |
WY |
https://health.wyo.gov/publichealth/infectious-disease-epidemiology-unit/disease/novel-coronavirus/ |
https://health.wyo.gov/publichealth/infectious-disease-epidemiology-unit/disease/novel-coronavirus/ |
@health_wyoming |
No data |
False |
Wyoming positive counts were reduced by from 3/18 > 3/19. Negatives = Total - Positive. |
Wyoming |
WY |
https://health.wyo.gov/publichealth/infectious-disease-epidemiology-unit/disease/novel-coronavirus/ |
https://health.wyo.gov/publichealth/infectious-disease-epidemiology-unit/disease/novel-coronavirus/ |
google-states |
| 51 |
PR |
http://www.salud.gov.pr/Pages/coronavirus.aspx |
http://www.salud.gov.pr/Pages/coronavirus.aspx |
@DeptSaludPR |
No Data |
False |
New data dashboard available: https://estadisticas.pr/en/covid-19 |
Puerto Rico |
PR |
http://www.salud.gov.pr/Pages/coronavirus.aspx |
http://www.salud.gov.pr/Pages/coronavirus.aspx |
google-states |
| 52 |
VI |
https://doh.vi.gov/ |
https://doh.vi.gov/ |
@usvidoh |
Positives Only |
False |
Virgin Islands: Positives and deaths provided. As of 3/18 at 12:56PM, update time was listed for 5:30PM (in the future), so we used 0:00 as a default timestamp. |
Virgin Islands |
VI |
https://doh.vi.gov/ |
https://doh.vi.gov/ |
google-states |
| 53 |
GU |
https://ghs.guam.gov/coronavirus-covid-19 |
https://ghs.guam.gov/coronavirus-covid-19 |
@guamdphss |
All Data |
False |
Guam: Data conveyed in individual press releases |
Guam |
GU |
https://ghs.guam.gov/coronavirus-covid-19 |
https://ghs.guam.gov/coronavirus-covid-19 |
google-states |
| 54 |
MP |
https://www.chcc.gov.mp/coronavirusinformation.php |
https://www.chcc.gov.mp/coronavirusinformation.php |
@cnmichcc |
No Data |
False |
Mariana Islands: No data, no confirmed cases yet. |
Northern Mariana Islands |
MP |
https://www.chcc.gov.mp/coronavirusinformation.php |
https://www.chcc.gov.mp/coronavirusinformation.php |
google-states |
| 55 |
AS |
http://www.samoagovt.ws/2020/03/ministry-of-health-coronavirus-covid-19-update-14-march-2020/ |
http://www.samoagovt.ws/2020/03/ministry-of-health-coronavirus-covid-19-update-14-march-2020/ |
NaN |
No Data |
False |
Samoa: No data, no confirmed cases yet. |
American Samoa |
AS |
http://www.samoagovt.ws/2020/03/ministry-of-health-coronavirus-covid-19-update-14-march-2020/ |
http://www.samoagovt.ws/2020/03/ministry-of-health-coronavirus-covid-19-update-14-march-2020/ |
google-states |


| Class | Violations |
|---|---|
|
Pkgtools\Phppear\Command
Probably bugged warning
This component contains in theory 0.39 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Probably bugged |
|
Pkgtools\Phppear\Source
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 50) * Component uses 151 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 21) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.2 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 245 logical lines of code * Class has 330 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
Pkgtools\Phpcomposer\Source
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.05 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
Pkgtools\Base\Dependency
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 78) * Component uses 160 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 29) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.13 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 235 logical lines of code * Class has 352 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
Pkgtools\Base\Command
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 17) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.86 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
XML_Util
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (16, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=16) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 72) * Component uses 189 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 24) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.52 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 267 logical lines of code * Class has 689 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
System
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (9, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=12) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 108) * Component uses 256 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 19) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.86 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 366 logical lines of code * Class has 575 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (15, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=15) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 82) * Component uses 164 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 19) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.19 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 327 logical lines of code * Class has 632 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Error
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 18) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.47 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
PEAR_XMLParser
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 13) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.46 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
PEAR_Config
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (45, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=6) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 267) * Component uses 626 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.5 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1007 logical lines of code * Class has 1422 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_ChannelFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (50, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=5) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 206) * Component uses 514 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 29) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.95 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 862 logical lines of code * Class has 1165 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_ErrorStack
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 92) * Component uses 199 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 22) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.69 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 405 logical lines of code * Class has 776 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Common
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (31, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=18) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 54) * Component uses 145 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 15) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.48 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 320 logical lines of code * Class has 640 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Dependency2
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (25, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=4) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 331) * Component uses 859 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 82) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.94 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 909 logical lines of code * Class has 1048 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (13, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=4) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 67) * Component uses 183 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 24) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.39 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 269 logical lines of code * Class has 393 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Validate
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 75) * Component uses 294 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 41) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.88 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 357 logical lines of code * Class has 505 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Exception
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 53) * Component uses 138 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 17) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.08 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex class code Too complex method code Probably bugged |
|
PEAR_DependencyDB
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 123) * Component uses 282 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 29) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.39 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 489 logical lines of code * Class has 634 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Installer
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 334) * Component uses 779 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 91) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.77 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1218 logical lines of code * Class has 1504 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Frontend_CLI
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 155) * Component uses 328 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 39) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.63 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 551 logical lines of code * Class has 605 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Downloader
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 365) * Component uses 772 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 74) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 7.88 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1190 logical lines of code * Class has 1452 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Downloader_Package
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (38, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=6) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 392) * Component uses 1018 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 52) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.82 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1314 logical lines of code * Class has 1541 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Builder
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 78) * Component uses 244 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 41) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 284 logical lines of code * Class has 390 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_REST_10
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 200) * Component uses 508 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 57) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.31 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 604 logical lines of code * Class has 709 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_REST_11
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 69) * Component uses 147 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 50) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.08 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 215 logical lines of code * Class has 263 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_REST_13
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 99) * Component uses 203 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 53) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.47 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 258 logical lines of code * Class has 323 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Registry
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 393) * Component uses 1085 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 38) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.79 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1595 logical lines of code * Class has 2028 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_REST
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 87) * Component uses 265 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 40) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.05 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 305 logical lines of code * Class has 378 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Install
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 207) * Component uses 545 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 84) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.93 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 778 logical lines of code * Class has 871 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Remote
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 135) * Component uses 382 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 37) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.13 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 500 logical lines of code * Class has 534 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Config
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 67) * Component uses 184 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 21) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.05 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 252 logical lines of code * Class has 281 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Common
Probably bugged warning
This component contains in theory 0.82 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Probably bugged |
|
PEAR_Command_Package
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (17, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=3) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 155) * Component uses 516 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 32) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.82 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 723 logical lines of code * Class has 769 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Pickle
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 75) * Component uses 186 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 67) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.74 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 250 logical lines of code * Class has 284 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Channels
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (13, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=3) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 115) * Component uses 412 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.27 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 565 logical lines of code * Class has 631 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Command_Registry
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (8, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=3) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 242) * Component uses 652 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 125) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 7.14 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 860 logical lines of code * Class has 897 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Proxy
Probably bugged warning
This component contains in theory 0.43 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Probably bugged |
|
PEAR_Task_Postinstallscript
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 34) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.5 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
PEAR_Task_Replace
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 15) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.53 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
PEAR_Command
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (11, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=11) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 19) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.75 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Blob / God object Too complex method code Probably bugged |
|
PEAR_Packager
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 32) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.68 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
PEAR_PackageFile_v2
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (104, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=4) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 353) * Component uses 829 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.55 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1484 logical lines of code * Class has 1826 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_v2_rw
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 178) * Component uses 527 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 17) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.75 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 849 logical lines of code * Class has 1169 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_v2_Validator
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 474) * Component uses 886 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 77) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 11.52 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1624 logical lines of code * Class has 1737 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_Parser_v1
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 91) * Component uses 167 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 42) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.45 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 337 logical lines of code * Class has 419 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_Generator_v2
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 149) * Component uses 414 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 54) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.71 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 582 logical lines of code * Class has 770 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_Generator_v1
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (20, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=3) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 239) * Component uses 617 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 52) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.94 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 856 logical lines of code * Class has 1058 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_PackageFile_v1
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.
* object has lot of public methods (85, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=17) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 204) * Component uses 486 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 64) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.56 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 932 logical lines of code * Class has 1102 lines of code Maybe your class should not exceed 200 lines of logical code |
Blob / God object Too complex class code Too complex method code Probably bugged Too long |
|
PEAR_Installer_Role_Common
Probably bugged warning
This component contains in theory 0.37 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Probably bugged |
|
PEAR_Installer_Role
Probably bugged warning
This component contains in theory 0.48 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Probably bugged |
|
Console_Getopt
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 56) * Component uses 162 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 18) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.96 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex class code Too complex method code Probably bugged |
|
Archive_Tar
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 327) * Component uses 1086 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 66) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.96 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 1314 logical lines of code * Class has 1866 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
OS_Guess
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 47) * Component uses 137 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 25) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.99 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 200 logical lines of code * Class has 296 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
SebastianBergmann\PHPLOC\Analyser
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 150) * Component uses 302 operators Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 104) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.92 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 418 logical lines of code * Class has 478 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Too complex method code Probably bugged Too long |
|
SebastianBergmann\PHPLOC\ArgumentsBuilder
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 16) Maybe you should delegate some code to other objects or split complex method. |
Too complex method code |
|
SebastianBergmann\PHPLOC\Collector
Too long information
This class looks really long.
* Class has 209 logical lines of code * Class has 209 lines of code Maybe your class should not exceed 200 lines of logical code |
Too long |
|
SebastianBergmann\PHPLOC\Log\Text
Too complex method code error
This class looks really complex.
* Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.01 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class. |
Too complex method code Probably bugged |
|
SebastianBergmann\PHPLOC\Publisher
Too complex class code error
This class looks really complex.
* Algorithms are complex (Total cyclomatic complexity of class is 7) * Component uses 90 operators Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.9 bugs.
* Calculation is based on number of operators, operands, cyclomatic complexity * See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures * testsuites has dependency to this class. Maybe you should check your unit tests for this class.
Too long information
This class looks really long.
* Class has 293 logical lines of code * Class has 293 lines of code Maybe your class should not exceed 200 lines of logical code |
Too complex class code Probably bugged Too long |
| Package | Violations |
|---|---|
|
XML_Util
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.5) than 1 package(s) that it depends on. The packages that are more stable are * PEAR (0.75) |
Stable Dependencies Principle |
|
System
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.118) than 2 package(s) that it depends on. The packages that are more stable are * Console_Getopt (0.5) * PEAR (0.75) |
Stable Abstractions Principle Stable Dependencies Principle |
|
PEAR
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.75) than 1 package(s) that it depends on. The packages that are more stable are * Structures_Graph (0.75) |
Stable Dependencies Principle |
|
PEAR
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.167) than 1 package(s) that it depends on. The packages that are more stable are * PEAR (0.75) |
Stable Abstractions Principle Stable Dependencies Principle |
|
PEAR_ErrorStack
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract. |
Stable Abstractions Principle |
|
Console_Getopt
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.5) than 1 package(s) that it depends on. The packages that are more stable are * PEAR (0.75) |
Stable Dependencies Principle |
|
Archive_Tar
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.1) than 1 package(s) that it depends on. The packages that are more stable are * PEAR (0.75) |
Stable Abstractions Principle Stable Dependencies Principle |
|
App\Http\Controllers
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.
This package is more stable (0.3) than 1 package(s) that it depends on. The packages that are more stable are * App\Gateway (0.5) |
Stable Abstractions Principle Stable Dependencies Principle |
|
App\Repository
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.
This package is instable and abstract. |
Stable Abstractions Principle |


Item.
We denote the restriction on the magic carpet’s movement by the vector \((1,2)\text{.}\) By this we mean that if the magic carpet traveled “forward” for one hour, it would move along a “diagonal” path that would result in a displacement of 1 mile East and 2 miles North of its starting location.in-context


Chapter 2 Introduction
You can label chapter and section titles using {#label}
after them, e.g., we can reference Chapter 2. If you do not manually label them, there will be automatic labels anyway, e.g., Chapter ??.
Figures and tables with captions will be placed in figure
and table
environments, respectively.
par(mar = c(4, 4, .1, .1))
plot(pressure, type = 'b', pch = 19)
Reference a figure by its code chunk label with the fig:
prefix, e.g., see Figure 2.1. Similarly, you can reference tables generated from knitr::kable()
, e.g., see Table 2.1.
::kable(
knitrhead(iris, 20), caption = 'Here is a nice table!',
booktabs = TRUE
)
| Sepal.Length | Sepal.Width | Petal.Length | Petal.Width | Species |
|---|---|---|---|---|
| 5.1 | 3.5 | 1.4 | 0.2 | setosa |
| 4.9 | 3.0 | 1.4 | 0.2 | setosa |
| 4.7 | 3.2 | 1.3 | 0.2 | setosa |
| 4.6 | 3.1 | 1.5 | 0.2 | setosa |
| 5.0 | 3.6 | 1.4 | 0.2 | setosa |
| 5.4 | 3.9 | 1.7 | 0.4 | setosa |
| 4.6 | 3.4 | 1.4 | 0.3 | setosa |
| 5.0 | 3.4 | 1.5 | 0.2 | setosa |
| 4.4 | 2.9 | 1.4 | 0.2 | setosa |
| 4.9 | 3.1 | 1.5 | 0.1 | setosa |
| 5.4 | 3.7 | 1.5 | 0.2 | setosa |
| 4.8 | 3.4 | 1.6 | 0.2 | setosa |
| 4.8 | 3.0 | 1.4 | 0.1 | setosa |
| 4.3 | 3.0 | 1.1 | 0.1 | setosa |
| 5.8 | 4.0 | 1.2 | 0.2 | setosa |
| 5.7 | 4.4 | 1.5 | 0.4 | setosa |
| 5.4 | 3.9 | 1.3 | 0.4 | setosa |
| 5.1 | 3.5 | 1.4 | 0.3 | setosa |
| 5.7 | 3.8 | 1.7 | 0.3 | setosa |
| 5.1 | 3.8 | 1.5 | 0.3 | setosa |
You can write citations, too. For example, we are using the bookdown package (Xie 2021) in this sample book, which was built on top of R Markdown and knitr (Xie 2015).
C. elegans plate experiment
(Again: work out this exercise in a Rmarkdown file in your portfolio-project. You will need this later to put in your portfolio)
The data for this exercise was kindly supplied by J. Louter (INT/ILC) and was derived from an experiment in which adult C.elegans nematodes were exposed to varying concentrations of different compounds. The variables RawData (the outcome - number of offspring counted as an integer value, after incubation time), compName (the generic name of the compound/chemical), the compConcentration (the concentration of the compound), and the expType are the most important variables in this dataset.
A typical analysis with this data would be to run a dose-response analysis using a log-logistic model with estimates for the maximal, the minimal, the IC50 concentration and the slope at IC50. We will not go into the details but a good package to run such computations and create graphs in R is the {drc} package. See: and:. In the exercise below we will create some visualizations using {ggplot2}.
A. Review the following Excel file in the ./data/CE.LIQ.FLOW.062_Tidydata.xlsx (it’s here), by opening the file in Excel. See if you can spot anything peculiar about this file. Do not edit the file in any way. Just close it when you are done.  What types would you expect from the experimental description above. Have the data types been correctly assigned during the importing of the data into R?
typeof(ce_liq_flow_062$RawData)
## [1] "double"
typeof(ce_liq_flow_062$compName)
## [1] "character"
typeof(ce_liq_flow_062$compConcentration)
## [1] "character"
compConcentration should be numeric
D. Create a graph displaying a scatterplot for the CE.LIQ.FLOW.062_Tidydata.xlsx data, for the different compounds and the varying concentrations. Put the compConcentration on the x-axis, the DataRaw counts on the y-axis and assign a colour to each level in compName. Assign a different symbol (shape =) to each level in the expType variable. Try fixing the labels of the x-axis so that we can read them.
ggplot(data = ce_liq_flow_062, aes(x = compConcentration, y = RawData)) +
geom_point(aes(colour = compName, shape = compName)) +
scale_x_discrete(guide = guide_axis(angle = 45)) +
labs(title = "compConcentration is double")
## Warning: Removed 5 rows containing missing values (geom_point).
https://www.datanovia.com/en/blog/ggplot-point-shapes-best-tips/ https://stackoverflow.com/questions/1330989/rotating-and-spacing-axis-labels-in-ggplot2
E. When creating the plot under C), what happened with the ordering of the x-axis labels. Explain why this happens. Look at the data-type of the compConcentration column in the data again to find a clue. ze worden niet afgerond? omdat het characters zijn?
F. Correct the data-type of compConcentration to numeric and than look at the graph again. Use a log10 transformation on the x-axis to get a clear graph. Also, add a bit of jitter to the points in the graph so that points are not overlapping.
$compConcentration <- as.numeric(as.character(ce_liq_flow_062$compConcentration)) ce_liq_flow_062
## Warning: NAs introduced by coercion
typeof(ce_liq_flow_062$compConcentration)
## [1] "double"
<-ggplot(data = ce_liq_flow_062, aes(x = compConcentration, y = RawData)) +
log10_scatter geom_point(position=position_jitter(width=.1,height=0),aes(colour = compName, shape = compName)) +
scale_x_discrete(guide = guide_axis(angle = 45))+
labs(title = "compConcentration is numeric")
+ scale_x_log10() log10_scatter
## Scale for 'x' is already present. Adding another scale for 'x', which will
## replace the existing scale.
## Warning: Transformation introduced infinite values in continuous x-axis
## Warning: Removed 6 rows containing missing values (geom_point).
G.Fill in: (G) The positive control for this experiments is naphthale (H) The negative control for this experiment is S-medium.
I.Think about how you would analyze this experiment to learn whether there is indeed an effect of different concentrations on offspring count and whether the different compounds have a different curve (IC50). Write down you analysis as a step-wise plan
- kijk of de data normaal verdeeld is
- voer de bijbehorende statistische toets uit
J.Normalize the data for the controlNegative in such a way that the mean value for controlNegative is exactly equal to 1 and that all other values are expressed as a fraction thereof. Rerun your graphs with the normalized data.
H.Why would you want to take the step under J?
#Open Peer Review
This exercise is about identifying reproducibility issues in a scientific publication. We use the criteria for reproduciblity that are publically available via here
Transparency Criteria Definition Response Type Study Purpose A concise statement in the introduction of the article, often in the last paragraph, that establishes the reason the research was conducted. Also called the study objective. Binary Data Availability Statement A statement, in an individual section offset from the main body of text, that explains how or if one can access a study’s data. The title of the section may vary, but it must explicitly mention data; it is therefore distinct from a supplementary materials section. Binary Data Location Where the article’s data can be accessed, either raw or processed. Found Value Study Location Author has stated in the methods section where the study took place or the data’s country/region of origin. Binary; Found Value Author Review The professionalism of the contact information that the author has provided in the manuscript. Found Value Ethics Statement A statement within the manuscript indicating any ethical concerns, including the presence of sensitive data. Binary Funding Statement A statement within the manuscript indicating whether or not the authors received funding for their research. Binary Code Availability Authors have shared access to the most updated code that they used in their study, including code used for analysis. Binary Table clarification The Transparency Criteria are criteria you need to score the article of your choice for. Read them carefully and discuss with another course participant if you do not understand them. Each Tranparance criterion comes with a Definition that explains the criterion in more details. These descriptions are particularly helpful to understand what the criterium entails and what to look for in the article. The Response Type is the actual score
In this assisgment you need to find a scientific article yourself, using PubMed or another database or repository. Use only Open Access articles. Having an article in hand, go over the table above and score the article according the criteria. Be sure to select a primary article that presents a study using data from experimental work . This can be laboratory experiments or in silico experiments. Reviews and meta analysis are not suitable for this assignment
To guide your search you can choose between these topics
“Coronavirus / COVID-19” “The effects of compound on an organism / Toxicology” “The effectiveness of a drug or treatment in an animal study” “The effects of a compound investigated in a cell or organoid system”
https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>2917v2.full
Study Purpose : er wordt in de samenvatting kort uitgelegd wat voor belanger er is om dit onderzoek uit te voeren Data Availability Statement: niet aanwezig Data Location: er wordt wel bescreven hoe de data er uit moet zien en er zijn verwijzingen naar waar artikelen waar in wordt beschrevenhoe de data verzameld is. Er staat niet waar je de gebruikte data terug kan vinden. Study Location: in de materiaal en methode sectie staat geen informatie over waar het onderzoek is uitgevoerd Author Review: de gegevens van de auteurs zijn niet makkelij te verkrijgen, de namen van de auteurs staan boven aan het artkel maar verdere contact gegevens staan niet op de pagina zelf. Ethics Statement: in de introductie staat kort iets over de ethiek Funding Statement: er wordt niets gezegt over de financiering Code Availability: er wordt geen code gedeeld in het artikel
TIPS If you do not know where to start your literature search start here: https://www.biorxiv.org/ This assignment is not about the topic you select, so try to do that quickly You may want to cheat and select an article that scores TRUE on the Data Availability Statement, because that enables you to use the this article again in one of the next assignments. PART 1 To complete part 1, execute activity A to G
Initiate an empty RMarkdown file in your RStudio environment and provide author and title (after the title of this exercise) Search for a primary Open Access article on one of the above listed topics, using Pubmed Central Read the article diagonally to check if is indeed a primary article describing emperical scientific findings. Include the reference to this article in your Rmd file Score the article on the basis of the above ‘Repita’ criteria Write an Rmarkdown report on your findings, including the table above and some information about the article such as general aim, short methods and results. If data is available, try including some Store the source Rmd and knitted HTML in a folder called ‘Rmd’ in your course RStudio project. You will need it again later in the course PART 2 To complete this assignment you will have to execute activity H to P
Using the OSF website, select a project that addresses an aspect of the SARS-Cov-2 virus. Select a project that has a dataset and R-code shared in the project environment. Have a look at the code. Describe in your own words what the code intents to achieve. In terms of readibility of the code, how would you grade (1(very bad)-5(very good)) the code available. Download the code and the data to a new RStudio project Run the script or code that is available to reproduce at least 1 figure When you encounter errors or flaws in the script, try fixing them and record your changes. Taken together on a scale from 1 (very hard) to 5 (very easy), how much effort did it take you to reproduce the visualization from the project, report or article Generate an RMarkdown script that contains the details on the project you selected, the code you used to create the visualization and your score for reproducibility. resource: https://www.researchgate.net/publication/340244621_Reproducibility_and_reporting_practices_in_COVID-19_preprint_manuscripts/fulltext/5e81f9fd92851caef4ae37ba/Reproducibility-and-reporting-practices-in-COVID-19-preprint-manuscripts.pdf
#https://osf.io/gkcn7/
library(readxl)
#salmonellacfu <- read_excel("salmonella")


Katz’s career in fine art began in 1946, the number of works produced each year increased since then until the recent production break in 2014. The artwork’s average hammer price is the highest during the 2000-2010 at $1,003,669, where on average 10 paintings produced and supplied on the auction house. Due to the high media exposure in Katz’s recent production years, it is recommended to invest in artworks produced from 2000-2010.