anchor.diff:  CA2215,DisposeMethodsShouldCallBaseClassDispose,System.Runtime,#N/A,Dispose Methods Should Call Base Class Dispose,"If a type inherits from a disposable type, it must call the Dispose method of the base type from its own Dispose method.",Yes,37586,119,0.003166072,1445.01623,Usage,,Low,Yes,,,Dataflow
   CA2216,DisposableTypesShouldDeclareFinalizer,System.Runtime,#N/A,Disposable types should declare finalizer,"A type that implements System.IDisposable and has fields that suggest the use of unmanaged resources does not implement a finalizer, as described by Object.Finalize.",Yes,8011,13,0.001622769,2405.571878,Usage,,High,Yes,,,InternalUtilities
   RS0009,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Override Object.Equals(object) when implementing Iequatable,#N/A,,,,,,Reliability,,,Ported,,,
  -CA2218,OverrideGetHashCodeOnOverridingEquals,Microsoft.ApiDesignGuidelines,#N/A,Override GetHashCode on overriding Equals,"GetHashCode returns a value, based on the current instance, that is suited for hashing algorithms and data structures such as a hash table. Two objects that are the same type and are equal must return the same hash code.",Yes,34660,25,0.000721293,6294.018313,Usage,,High,Merge?,,,None
  +CA2218,OverrideGetHashCodeOnOverridingEquals,Microsoft.ApiDesignGuidelines,#N/A,Override GetHashCode on overriding Equals,"GetHashCode returns a value, based on the current instance, that is suited for hashing algorithms and data structures such as a hash table. Two objects that are the same type and are equal must return the same hash code.",Yes,34660,25,0.000721293,6294.018313,Usage,,High,Yes,,Fixer should create method that throws NotImplementedException. Implementer should check if the compiler gives this warning.,None
   CA2219,DoNotRaiseExceptionsInExceptionClauses,System.Runtime,#N/A,Do not raise exceptions in exception clauses,"When an exception is raised in a finally or fault clause, the new exception hides the active exception. When an exception is raised in a filter clause, the run time silently catches the exception. This makes the original error difficult to detect and debug.",Yes,14661,36,0.002455494,1696.670124,Usage,,High,Yes,,,None
   CA2220,FinalizersShouldCallBaseClassFinalizer,System.Runtime,#N/A,Finalizers should call base class finalizer,"Finalization must be propagated through the inheritance hierarchy. To guarantee this, types must call their base class Finalize method in their own Finalize method.",Yes,47,0,0,,Usage,,Low,Yes,,,None
   CA2221,FinalizersShouldBeProtected,System.Runtime,#N/A,Finalizers should be protected,Finalizers must use the family access modifier.,Yes,10,0,0,,Usage,,Low,Cut,,,N/A
   CA2222,DoNotDecreaseInheritedMemberVisibility,Microsoft.ApiDesignGuidelines,#N/A,Do not decrease inherited member visibility,You should not change the access modifier for inherited members. Changing an inherited member to private does not prevent callers from accessing the base class implementation of the method.,Yes,64588,185,0.002864309,1679.34101,Usage,,High,Yes,,,None
  -CA2223,MembersShouldDifferByMoreThanReturnType,Microsoft.ApiDesignGuidelines,#N/A,Members should differ by more than return type,"Although the common language runtime allows the use of return types to differentiate between otherwise identical members, this feature is not in the Common Language Specification, nor is it a common feature of .NET programming languages.",Yes,12,1,0.083333333,12.95017495,Usage,,High,,,,None
  -CA2224,OverrideEqualsOnOverloadingOperatorEquals,Microsoft.ApiDesignGuidelines,#N/A,Override Equals on overloading operator equals,A public type implements the equality operator but does not override Object.Equals.,Yes,7619,11,0.001443759,2688.743696,Usage,,High,Merge?,,,None
  +CA2223,MembersShouldDifferByMoreThanReturnType,Microsoft.ApiDesignGuidelines,#N/A,Members should differ by more than return type,"Although the common language runtime allows the use of return types to differentiate between otherwise identical members, this feature is not in the Common Language Specification, nor is it a common feature of .NET programming languages.",Yes,12,1,0.083333333,12.95017495,Usage,,High,No,,"Hardly ever fires, can't violate it in C# and VB, and Roslyn can't examine anything else.",None
  +CA2224,OverrideEqualsOnOverloadingOperatorEquals,Microsoft.ApiDesignGuidelines,#N/A,Override Equals on overloading operator equals,A public type implements the equality operator but does not override Object.Equals.,Yes,7619,11,0.001443759,2688.743696,Usage,,High,Yes,,Fixer should create method that throws NotImplementedException. Implementer should check if the compiler gives this warning.,None
   CA2225,OperatorOverloadsHaveNamedAlternates,Microsoft.ApiDesignGuidelines,#N/A,Operator overloads have named alternates,"An operator overload was detected, and the expected named alternative method was not found. The named alternative member provides access to the same functionality as the operator and is provided for developers who program in languages that do not support overloaded operators.",Yes,71083,1385,0.019484265,249.009433,Usage,,High,Yes,,,HardCoded list of alternates
   CA2226,OperatorsShouldHaveSymmetricalOverloads,Microsoft.ApiDesignGuidelines,#N/A,Operators should have symmetrical overloads,A type implements the equality or inequality operator and does not implement the opposite operator.,Yes,47,0,0,,Usage,,High,Yes,,,None
   RS0013,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Do not invoke Diagnostic.Descriptor,"Accessing the Descriptor property of Diagnostic in compiler layer leads to unnecessary string allocations for fields of the descriptor that are not utilized in command line compilation. Hence, you should avoid accessing the Descriptor of the compiler diagnostics here. Instead you should directly access these properties off the Diagnostic type.",,,,,,Performance,,,Ported,,,
   CA2228,DoNotShipUnreleasedResourceFormats,System.Runtime,#N/A,Do not ship unreleased resource formats,Resource files that were built by using prerelease versions of the .NET Framework might not be usable by supported versions of the .NET Framework.,Yes,2033,45,0.022134776,149.4542954,Usage,,High,Cut,,,N/A
   RS0016,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Add public types and members to the declared API,"All public types and members should be declared in PublicAPI.txt. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes.",,,,,,ApiDesign,,,Ported,,,
  -CA2230,UseParamsForVariableArguments,Microsoft.ApiDesignGuidelines,#N/A,Use params for variable arguments,A public or protected type contains a public or protected method that uses the VarArgs calling convention instead of the params keyword.,Yes,126,8,0.063492063,33.08083609,Usage,,High,,,,None
  +CA2230,UseParamsForVariableArguments,Microsoft.ApiDesignGuidelines,#N/A,Use params for variable arguments,A public or protected type contains a public or protected method that uses the VarArgs calling convention instead of the params keyword.,Yes,126,8,0.063492063,33.08083609,Usage,,High,No,,"This is about __arglist, rarely used.",None
   CA2231,OverloadOperatorEqualsOnOverridingValueTypeEquals,Microsoft.ApiDesignGuidelines,System.Runtime.Analyzers,Overload operator equals on overriding value type Equals,"In most programming languages there is no default implementation of the equality operator (==) for value types. If your programming language supports operator overloads, you should consider implementing the equality operator. Its behavior should be identical to that of Equals",Yes,15312,25,0.001632706,2563.248351,Usage,,High,Yes,,,None
   CA2232,MarkWindowsFormsEntryPointsWithStaThread,Desktop,#N/A,Mark Windows Forms entry points with STAThread,"STAThreadAttribute indicates that the COM threading model for the application is a single-threaded apartment. This attribute must be present on the entry point of any application that uses Windows Forms; if it is omitted, the Windows components might not work correctly.",Yes,17032,43,0.002524659,1675.974803,Usage,,Low,Yes,,,None
  -CA2233,OperationsShouldNotOverflow,System.Runtime,#N/A,Operations should not overflow,You should not perform arithmetic operations without first validating the operands. This makes sure that the result of the operation is not outside the range of possible values for the data types that are involved.,Yes,177875,717,0.004030921,1302.460516,Usage,,High,,,,IOperation
  +CA2233,OperationsShouldNotOverflow,System.Runtime,#N/A,Operations should not overflow,You should not perform arithmetic operations without first validating the operands. This makes sure that the result of the operation is not outside the range of possible values for the data types that are involved.,Yes,177875,717,0.004030921,1302.460516,Usage,,High,No,,Very noisy,IOperation
   CA2234,PassSystemUriObjectsInsteadOfStrings,Microsoft.ApiDesignGuidelines,#N/A,Pass system uri objects instead of strings,"A call is made to a method that has a string parameter whose name contains ""uri"", ""URI"", ""urn"", ""URN"", ""url"", or ""URL"". The declaring type of the method contains a corresponding method overload that has a System.Uri parameter.",Yes,197362,824,0.004175069,1268.305585,Usage,,High,Yes,,,WordParser
   RS0017,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Remove deleted types and members from the declared API,"When removing a public type or member the corresponding entry in PublicAPI.txt should also be removed. This draws attention to API changes in the code reviews and source control history, and helps prevent breaking changes.",,,,,,ApiDesign,,,Ported,,,
   CA2236,CallBaseClassMethodsOnISerializableTypes,Desktop,#N/A,Call base class methods on ISerializable types,"To fix a violation of this rule, call the base type GetObjectData method or serialization constructor from the corresponding derived type method or constructor.",Yes,23555,57,0.002419868,1806.744169,Usage,,Low,Yes,,,IOperation
  
positive.code: CA2100,ReviewSqlQueriesForSecurityVulnerabilities,Desktop,#N/A,Review SQL queries for security vulnerabilities,A method sets the System.Data.IDbCommand.CommandText property by using a string that is built from a string argument to the method. This rule assumes that the string argument contains user input. A SQL command string that is built from user input is vulnerable to SQL injection attacks.,Yes,418391,3364,0.008040326,699.1734406,Security,,Low,No,,,Dataflow
  RS0022,#N/A,Microsoft.ApiDesignGuidelines,Roslyn.Diagnostics.Analyzers,Constructor make noninheritable base class inheritable,"When a base class is noninheritable because its constructor is internal, a derived class should not make it inheritable by having a public or protected constructor.",,,,,,ApiDesign,,,Ported,,,
  CA2102,CatchNonClsCompliantExceptionsInGeneralHandlers,System.Runtime,#N/A,Catch non-CLSCompliant exceptions in general handlers,A member in an assembly that is not marked by using the RuntimeCompatibilityAttribute or is marked RuntimeCompatibility(WrapNonExceptionThrows = false) contains a catch block that handles System.Exception and does not contain an immediately following general catch block.,Yes,2400,11,0.004583333,737.5006346,Security,,Low,No,,Not relevant any more because the CLR wraps non-Exception-derived throws,
  CA2103,ReviewImperativeSecurity,Desktop,#N/A,Review imperative security,A method uses imperative security and might be constructing the permission by using state information or return values that can change as long as the demand is active. Use declarative security whenever possible.,Yes,11291,80,0.007085289,571.9925201,Security,,Low,,,,
  CA2104,DoNotDeclareReadOnlyMutableReferenceTypes,System.Runtime,#N/A,Do not declare read only mutable reference types,An externally visible type contains an externally visible read-only field that is a mutable reference type. A mutable type is a type whose instance data can be modified.,Yes,292444,8727,0.029841611,183.1684881,Security,,Low,Cut,,,Hardcoded list of immutable types
  CA2105,ArrayFieldsShouldNotBeReadOnly,System.Runtime,#N/A,Array fields should not be read only,"When you apply the read-only (ReadOnly in Visual Basic) modifier to a field that contains an array, the field cannot be changed to reference a different array. However, the elements of the array that are stored in a read-only field can be changed.",Yes,58839,177,0.003008209,1585.549919,Security,,Low,Yes,,Some other rule about not having visible fields would have to be suppressed before this would be the only indication of a problem.,
  CA2106,SecureAsserts,Desktop,#N/A,Secure asserts,A method asserts a permission and no security checks are performed on the caller. Asserting a security permission without performing any security checks can leave an exploitable security weakness in your code.,Yes,13428,138,0.010277033,401.6734505,Security,,Low,,,,
  CA2107,ReviewDenyAndPermitOnlyUsage,Desktop,#N/A,Review deny and permit only usage,The PermitOnly method and CodeAccessPermission.Deny security actions should be used only by those who have an advanced knowledge of .NET Framework security. Code that uses these security actions should undergo a security review.,Yes,938,16,0.017057569,174.2453914,Security,,Low,,,,
  CA2108,ReviewDeclarativeSecurityOnValueTypes,Desktop,#N/A,Review declarative security on value types,A public or protected value type is secured by Data Access or Link Demands.,Yes,136,0,0,,Security,,Low,,,,
  CA2109,ReviewVisibleEventHandlers,System.Runtime,#N/A,Review visible event handlers,A public or protected event-handling method was detected. Event-handling methods should not be exposed unless absolutely necessary.,Yes,249217,1465,0.005878411,918.0333759,Security,,High,,,,None
  CA2111,PointersShouldNotBeVisible,System.Runtime,#N/A,Pointers should not be visible,"A pointer is not private, internal, or read-only. Malicious code can change the value of the pointer, which potentially gives access to arbitrary locations in memory or causes application or system failures.",Yes,49556,248,0.005004439,938.1862479,Security,,Low,,,,
  CA2112,SecuredTypesShouldNotExposeFields,Desktop,#N/A,Secured types should not expose fields,"A public or protected type contains public fields and is secured by Link Demands. If code has access to an instance of a type that is secured by a link demand, the code does not have to satisfy the link demand to access the fields of the type.",Yes,9409,0,0,,Security,,Low,,,,
  CA2114,MethodSecurityShouldBeASupersetOfType,Desktop,#N/A,Method security should be a superset of type,A method should not have both method-level and type-level declarative security for the same action.,Yes,7,0,0,,Security,,Low,,,,
  CA2115,CallGCKeepAliveWhenUsingNativeResources,System.Runtime.InteropServices,#N/A,Call GC.KeepAlive when using native resources,This rule detects errors that might occur because an unmanaged resource is being finalized while it is still being used in unmanaged code.,Yes,21,153,7.285714286,0.18148108,Security,,Low,,,,
  CA2116,AptcaMethodsShouldOnlyCallAptcaMethods,System.Runtime,#N/A,Aptca methods should only call aptca methods,"When the APTCA (AllowPartiallyTrustedCallersAttribute) is present on a fully trusted assembly, and the assembly executes code in another assembly that does not allow for partially trusted callers, a security exploit is possible.",Yes,20253,864,0.042660347,100.9482975,Security,,Low,,,,
  CA2117,AptcaTypesShouldOnlyExtendAptcaBaseTypes,System.Runtime,#N/A,Aptca types should only extend aptca base types,"When the APTCA is present on a fully trusted assembly, and a type in the assembly inherits from a type that does not allow for partially trusted callers, a security exploit is possible.",Yes,6740,43,0.006379822,600.1201791,Security,,Low,,,,
  CA2118,ReviewSuppressUnmanagedCodeSecurityUsage,System.Runtime.InteropServices,#N/A,Review suppress unmanaged code security usage,"This attribute is primarily used to increase performance; however, the performance gains come with significant security risks. If you place the attribute on public members that call native methods, the callers in the call stack (other than the immediate caller) do not need unmanaged code permission to execute unmanaged code. Depending on the public member's actions and input handling, it might allow untrustworthy callers to access functionality normally restricted to trustworthy code.",Yes,13584,539,0.039679034,104.1614989,Security,,Low,,,,
  CA2119,SealMethodsThatSatisfyPrivateInterfaces,System.Runtime,#N/A,Seal methods that satisfy private interfaces,"An inheritable public type provides an overridable method implementation of an internal (Friend in Visual Basic) interface. To fix a violation of this rule, prevent the method from being overridden outside the assembly.",Yes,16649,76,0.004564839,924.7617285,Security,,Low,,,,
  CA2120,SecureSerializationConstructors,Desktop,#N/A,Secure serialization constructors,"This type has a constructor that takes a System.Runtime.Serialization.SerializationInfo object and a System.Runtime.Serialization.StreamingContext object (the signature of the serialization constructor). This constructor is not secured by a security check, but one or more of the regular constructors in the type are secured.",Yes,33,26,0.787878788,1.927344616,Security,,Low,,,,
  CA2121,StaticConstructorsShouldBePrivate,System.Runtime,#N/A,Static constructors should be private,"The system calls the static constructor before the first instance of the type is created or any static members are referenced. If a static constructor is not private, it can be called by code other than the system. Depending on the operations that are performed in the constructor, this can cause unexpected behavior.",Yes,44,0,0,,Security,,Low,,,,
  CA2122,DoNotIndirectlyExposeMethodsWithLinkDemands,Desktop,#N/A,Do not indirectly expose methods with link demands,A public or protected member has Link Demands and is called by a member that does not perform any security checks. A link demand checks the permissions of the immediate caller only.,Yes,733224,7044,0.009606887,610.5241757,Security,,High,,,,FxCopSDKUtilities
  CA2123,OverrideLinkDemandsShouldBeIdenticalToBase,System.Runtime,#N/A,Override link demands should be identical to base,"This rule matches a method to its base method, which is either an interface or a virtual method in another type, and then compares the link demands on each. If this rule is violated, a malicious caller can bypass the link demand just by calling the unsecured method.",No,138994,437,0.003144021,1635.802273,Security,,High,,,,FxCopSDKUtilties
  CA2124,WrapVulnerableFinallyClausesInOuterTry,Desktop,#N/A,Wrap vulnerable finally clauses in outer try,A public or protected method contains a try/finally block. The finally block appears to reset the security state and is not itself enclosed in a finally block.,Yes,2527,5,0.001978631,1719.676689,Security,,Low,,,,
  CA2126,TypeLinkDemandsRequireInheritanceDemands,Desktop,#N/A,Type link demands require inheritance demands,A public unsealed type is protected by using a link demand and has an overridable method. Neither the type nor the method is protected by using an inheritance demand.,Yes,3318,7,0.002109705,1668.895405,Security,,Low,,,,
  CA2130,ConstantsShouldBeTransparent,System.Runtime,#N/A,Security critical constants should be transparent,Transparency enforcement is not enforced for constant values because compilers inline constant values so that no lookup is required at run time. Constant fields should be security transparent so that code reviewers do not assume that transparent code cannot access the constant.,No,7,0,0,,Security,,Low,,,,
  CA2131,CriticalTypesMustNotParticipateInTypeEquivalence,System.Runtime,#N/A,Security critical types may not participate in type equivalence,"A type participates in type equivalence and either the type itself, or a member or field of the type, is marked by using the SecurityCriticalAttribute attribute. This rule occurs on any critical types or types that contain critical methods or fields that are participating in type equivalence. When the CLR detects such a type, it does not load it with a TypeLoadException at run time. Typically, this rule is raised only when users implement type equivalence manually instead of in by relying on tlbimp and the compilers to do the type equivalence.",No,7,0,0,,Security,,Low,,,,
  CA2132,DefaultConstructorsMustHaveConsistentTransparency,System.Runtime,#N/A,Default constructors must be at least as critical as base type default constructors,"Types and members that have the SecurityCriticalAttribute cannot be used by Silverlight application code. Security-critical types and members can be used only by trusted code in the .NET Framework for Silverlight class library. Because a public or protected construction in a derived class must have the same or greater transparency than its base class, a class in an application cannot be derived from a class marked as SecurityCritical.",No,467,0,0,,Security,,Low,,,,
  CA2133,DelegatesMustBindWithConsistentTransparency,System.Runtime,#N/A,Delegates must bind to methods with consistent transparency,This warning is raised on a method that binds a delegate that is marked by using the SecurityCriticalAttribute to a method that is transparent or that is marked by using the SecuritySafeCriticalAttribute. The warning also is raised on a method that binds a delegate that is transparent or safe-critical to a critical method.,No,69,0,0,,Security,,Low,,,,
  CA2134,MethodsMustOverrideWithConsistentTransparency,System.Runtime,#N/A,Methods must keep consistent transparency when overriding base methods,This rule is raised when a method marked by using the SecurityCriticalAttribute overrides a method that is transparent or marked by using the SecuritySafeCriticalAttribute. The rule also is raised when a method that is transparent or marked by using the SecuritySafeCriticalAttribute overrides a method that is marked by using a SecurityCriticalAttribute. The rule is applied when overriding a virtual method or implementing an interface.,No,3916,5,0.001276813,2813.914389,Security,,Low,,,,
  CA2135,SecurityRuleSetLevel2MethodsShouldNotBeProtectedWithLinkDemands,System.Runtime,#N/A,Level2 methods should not be protected with link demands,"LinkDemands are deprecated in the level 2 security rule set. Instead of using LinkDemands to enforce security at just-in-time (JIT) compilation time, mark the methods, types, and fields with the SecurityCriticalAttribute attribute.",No,72950,390,0.005346127,909.6351163,Security,,Low,,,,
  CA2136,TransparencyAnnotationsShouldNotConflict,System.Runtime,#N/A,Members should not have conflicting transparency annotations,"Critical code cannot occur in a 100 percent?transparent assembly. This rule analyzes 100 percent?transparent assemblies for any SecurityCritical annotations at the type, field, and method levels.",No,6481,114,0.017589878,216.6951925,Security,,Low,,,,
  CA2137,TransparentMethodsMustBeVerifiable,System.Runtime,#N/A,Transparent methods must contain only verifiable IL,"A method contains unverifiable code or returns a type by reference. This rule is raised on attempts by security transparent code to execute unverifiable microsoft intermediate language (MISL). However, the rule does not contain a full IL verifier, and instead uses heuristics to catch most violations of MSIL verification.",No,124,0,0,,Security,,Low,,,,
  CA2138,TransparentMethodsMustNotCallSuppressUnmanagedCodeSecurityMethods,System.Runtime,#N/A,Transparent methods must not call methods with the SuppressUnmanagedCodeSecurity attribute,A security transparent method calls a method that is marked by using the SuppressUnmanagedCodeSecurityAttribute attribute.,No,230,0,0,,Security,,Low,,,,
  CA2139,TransparentMethodsMustNotHandleProcessCorruptingExceptions,System.Runtime,#N/A,Transparent methods may not use the HandleProcessCorruptingExceptions attribute,"This rule is raised by any method that is transparent and attempts to handle a process corrupting exception by using the HandleProcessCorruptedStateExceptionsAttribute attribute. A process corrupting exception is a CLR version 4.0 exception classification of exceptions such as AccessViolationException. The HandleProcessCorruptedStateExceptionsAttribute attribute may be used only by security critical methods, and will be ignored if it is applied to a transparent method.",No,35,0,0,,Security,,Low,,,,
  CA2140,TransparentMethodsMustNotReferenceCriticalCode,System.Runtime,#N/A,Transparent code must not reference security critical items,"Methods that are marked by SecurityTransparentAttribute call nonpublic members that are marked as SecurityCritical. This rule analyzes all methods and types in an assembly that is mixed transparent/critical, and flags any calls from transparent code to nonpublic critical code that are not marked as SecurityTreatAsSafe.",No,13305,64,0.004810222,857.3440307,Security,,Low,,,,
  CA2141,TransparentMethodsMustNotSatisfyLinkDemands,System.Runtime,#N/A,Transparent methods must not satisfy LinkDemands,"A security transparent method calls a method in an assembly that is not marked by using the APTCA, or a security transparent method satisfies a LinkDemand for a type or a method.",No,16361,245,0.014974635,281.3965015,Security,,Low,,,,
  CA2142,TransparentMethodsShouldNotBeProtectedWithLinkDemands,System.Runtime,#N/A,Transparent code should not be protected with LinkDemands,"This rule is raised on transparent methods that require LinkDemands to access them. Security transparent code should not be responsible for verifying the security of an operation, and therefore should not demand permissions.",No,3330,18,0.005405405,651.6521832,Security,,Low,,,,
  CA2143,TransparentMethodsShouldNotDemand,System.Runtime,#N/A,Transparent methods should not use security demands,"Security transparent code should not be responsible for verifying the security of an operation, and therefore should not demand permissions. Security transparent code should use full demands to make security decisions and safe-critical code should not rely on transparent code to have made the full demand.",No,13049,22,0.001685953,2441.098513,Security,,Low,,,,
  CA2144,TransparentMethodsShouldNotLoadAssembliesFromByteArrays,System.Runtime,#N/A,Transparent code should not load assemblies from byte arrays,"The security review for transparent code is not as complete as the security review for critical code because transparent code cannot perform security sensitive actions. Assemblies that are loaded from a byte array might not be noticed in transparent code, and that byte array might contain critical, or more important safe-critical code, that does have to be audited.",No,72,0,0,,Security,,Low,,,,
  CA2145,TransparentMethodsShouldNotUseSuppressUnmanagedCodeSecurity,System.Runtime,#N/A,Transparent methods should not be decorated with the SuppressUnmanagedCodeSecurityAttribute,Methods that are decorated by the SuppressUnmanagedCodeSecurityAttribute attribute have an implicit LinkDemand put upon any method that calls it. This LinkDemand requires that the calling code be security critical. Marking the method that uses SuppressUnmanagedCodeSecurity by using the SecurityCriticalAttribute attribute makes this requirement more obvious for callers of the method.,No,155,0,0,,Security,,Low,,,,
  CA2146,TypesMustBeAtLeastAsCriticalAsBaseTypes,System.Runtime,#N/A,Types must be at least as critical as their base types and interfaces,"This rule is raised when a derived type has a security transparency attribute that is not as critical as its base type or implemented interface. Only critical types can derive from critical base types or implement critical interfaces, and only critical or safe-critical types can derive from safe-critical base types or implement safe-critical interfaces.",No,2865,2,0.00069808,4952.331027,Security,,Low,,,,
  CA2147,TransparentMethodsMustNotUseSecurityAsserts,System.Runtime,#N/A,Transparent methods may not use security asserts,"This rule analyzes all methods and types in an assembly that is either 100 percent?transparent or mixed transparent/critical, and flags any declarative or imperative use of Assert.",No,91,0,0,,Security,,Low,,,,
  CA2149,TransparentMethodsMustNotCallNativeCode,System.Runtime,#N/A,Transparent methods must not call into native code,"This rule is raised on any transparent method that calls directly into native code (for example, through a P/Invoke). Violations of this rule lead to a MethodAccessException in the level 2 transparency model and a full demand for UnmanagedCode in the level 1 transparency model.",No,4351,61,0.014019766,259.5328049,Security,,Low,,,,
  CA2150,TransparentCodeMustNotUseCriticalAttributes,System.Runtime,#N/A,#N/A,#N/A,No,,,,,,,Low,,,,
  CA2151,FieldsWithCriticalTypesShouldBeCritical,System.Runtime,#N/A,#N/A,#N/A,No,,,,,,,Low,,,,
  RS0006,#N/A,Microsoft.Composition,Roslyn.Diagnostics.Analyzers,Do not mix attributes from different versions of MEF,#N/A,,,,,,Reliability,,,Ported,,,
  RS0023,#N/A,Microsoft.Composition,Roslyn.Diagnostics.Analyzers,Parts exported with MEFv2 must be marked as Shared,#N/A,,,,,,Reliability,,,Ported,,,
  RS0001,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Use SpecializedCollections.EmptyEnumerable(),#N/A,,,,,,Performance,,,Ported,,,
  CA2202,DoNotDisposeObjectsMultipleTimes,System.Runtime,#N/A,Do not dispose objects multiple times,A method implementation contains code paths that could cause multiple calls to System.IDisposable.Dispose or a Dispose equivalent (such as a Close() method on some types) on the same object.,Yes,1034185,2477,0.002395123,2511.18582,Usage,,High,,,,Dataflow
  CA2204,LiteralsShouldBeSpelledCorrectly,Text,#N/A,Literals should be spelled correctly,A literal string in a method body contains one or more words that are not recognized by the Microsoft spelling checker library.,Yes,1364858,19401,0.014214666,431.6026604,Naming,,Low,,,,Dataflow
  CA2205,UseManagedEquivalentsOfWin32Api,System.Runtime.InteropServices,#N/A,Use managed equivalents of win32 api,An operating system invoke method is defined and a method that has the equivalent functionality is located in the .NET Framework class library.,Yes,28980,117,0.004037267,1105.227445,Usage,,Low,Yes,,,None
  RS0002,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Use SpecializedCollections.SingletonEnumerable(),#N/A,,,,,,Performance,,,Ported,,,
  CA2208,InstantiateArgumentExceptionsCorrectly,System.Runtime,#N/A,Instantiate argument exceptions correctly,"A call is made to the default (parameterless) constructor of an exception type that is or derives from ArgumentException, or an incorrect string argument is passed to a parameterized constructor of an exception type that is or derives from ArgumentException.",Yes,774590,2637,0.003404382,1729.850661,Usage,,High,,,,IOperation
  CA2209,AssembliesShouldDeclareMinimumSecurity,Desktop,#N/A,Assemblies should declare minimum security,"Assemblies specify security permission requests to communicate to administrators the minimum permissions that are required to execute the assembly, and to limit security vulnerabilities caused by mistakenly omitting demands at the type and member level. ",,7023,203,0.028905026,133.0745256,Security,,Low,Cut,,Deprecated rule,
  CA2210,AssembliesShouldHaveValidStrongNames,Microsoft.ApiDesignGuidelines,#N/A,Assemblies should have valid strong names,"The strong name protects clients from unknowingly loading an assembly that has been tampered with. Assemblies without strong names should not be deployed outside very limited scenarios. If you share or distribute assemblies that are not correctly signed, the assembly can be tampered with, the common language runtime might not load the assembly, or the user might have to disable verification on his or her computer.",Yes,2955771,8737,0.002955912,2189.060439,Design,,High,,,,None
  CA2211,NonConstantFieldsShouldNotBeVisible,Microsoft.ApiDesignGuidelines,#N/A,Non-constant fields should not be visible,Static fields that are neither constants nor read-only are not thread-safe. Access to such a field must be carefully controlled and requires advanced programming techniques to synchronize access to the class object.,Yes,752431,8608,0.011440252,513.6658574,Usage,,High,Yes,,,None
  CA2212,DoNotMarkServicedComponentsWithWebMethod,Desktop,#N/A,Do not mark serviced components with WebMethod,"A method in a type that inherits from System.EnterpriseServices.ServicedComponent is marked by using System.Web.Services.WebMethodAttribute. Because WebMethodAttribute and a ServicedComponent method have conflicting behavior and requirements for context and transaction flow, the behavior of the method will be incorrect in some scenarios.",Yes,26,0,0,,Usage,,Low,Yes,,,None
  RS0004,#N/A,Roslyn.Diagnostics,Roslyn.Diagnostics.Analyzers,Invoke the correct property to ensure correct use site diagnostics.,#N/A,,,,,,Usage,,,Ported,,,
  
negative.code: CA1704,IdentifiersShouldBeSpelledCorrectly,Text,#N/A,Identifiers should be spelled correctly,The name of an externally visible identifier contains one or more words that are not recognized by the Microsoft spelling checker library.,Yes,4050045,134475,0.033203335,198.9998864,Naming,High,Low,Yes,,See if StyleCop has implemented it,NamingService
  CA1705,LongAcronymnsShouldBePascalBased,Microsoft.ApiDesignGuidelines,#N/A,Long acronyms should be pascal-cased,"This rule assumes it has found an acronym when the name contains four uppercase letters in a row, or at the end of the name, three uppercase letters in a row. By convention, two-letter acronyms use all uppercase letters, and acronyms of three or more characters use Pascal casing. The following examples conform to this naming convention: 'DB', 'CR', 'Cpa', and 'Ecma'. The following examples violate the convention: 'Io', 'XML', and 'DoD', and for non-parameter names, 'xp' and 'cpl'. Naming conventions provide a common look for libraries that target the common language runtime. This reduces the learning curve required for new software libraries, and increases customer confidence that the library was developed by someone with expertise in developing managed code.",,2574,90,0.034965035,97.54340432,Naming,,Low,Cut,,Deprecated rule (replaced by 1709),
  CA1706,ShortAcronymsShouldBeUpperCase,Microsoft.ApiDesignGuidelines,#N/A,Short acronyms should be uppercase,"This rule splits the name into words based on the casing and checks any two-letter words against a list of common two-letter words, such as ""In"" or ""My"". If a match is not found, the word is assumed to be an acronym. For parameters, the first word is ignored due to the camel casing convention used for parameter names. By convention, two-letter acronyms use all uppercase letters, and acronyms of three or more characters use Pascal casing. The following examples conform to this naming convention: 'DB', 'CR', 'Cpa', and 'Ecma'. The following examples violate the convention: 'Io', 'XML', and 'DoD', and for non-parameter names, 'xp' and 'cpl'. 'ID' is special-cased to cause a violation of this rule. 'Id' is not an acronym but is an abbreviation for 'identification'. Naming conventions provide a common look for libraries that target the common language runtime. This reduces the learning curve required for new software libraries, and increases customer confidence that the library was developed by someone with expertise in developing managed code.",,470,2,0.004255319,627.9429966,Naming,,Low,Cut,,Deprecated rule (replaced by 1709),
  CA1707,IdentifiersShouldNotContainUnderscores,Microsoft.ApiDesignGuidelines,#N/A,Identifiers should not contain underscores,"By convention, identifier names do not contain the underscore (_) character. This rule checks namespaces, types, members, and parameters.",Yes,1216136,42995,0.035353776,172.1168937,Naming,High,Low,,,See if StyleCop has implemented it,None
  CA1060,MovePInvokesToNativeMethodsClass,Microsoft.ApiDesignGuidelines,System.Runtime.InteropServices.Analyzers,Move pinvokes to native methods class,"Platform Invocation methods, such as those that are marked by using the System.Runtime.InteropServices.DllImportAttribute attribute, or methods that are defined by using the Declare keyword in Visual Basic, access unmanaged code. These methods should be of the NativeMethods, SafeNativeMethods, or UnsafeNativeMethods class.",Yes,377447,2739,0.007256648,768.5168157,Design,,High,Ported,,,
  CA1709,IdentifiersShouldBeCasedCorrectly,Microsoft.ApiDesignGuidelines,#N/A,Identifiers should be cased correctly,"By convention, parameter names use camel casing and namespace, type, and member names use Pascal casing.",Yes,3261791,137633,0.04219553,154.3636525,Naming,,Low,Yes,,See if StyleCop has implemented it,NamingService
  CA1710,IdentifiersShouldHaveCorrectSuffix,Microsoft.ApiDesignGuidelines,#N/A,Identifiers should have correct suffix,"By convention, the names of types that extend certain base types or that implement certain interfaces, or types that are derived from these types, have a suffix that is associated with the base type or interface.",Yes,597568,3205,0.005363406,1076.999758,Naming,,High,,,See if StyleCop has implemented it,None
  