anchor.diff:  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,SecurityTransparentCodeShouldNotAssert,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,,,,
  +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,FieldsWithCriticalTypesShouldBeCriticalFxCopRule,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,,,
  
positive.code: 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
  CA2110,AssembliesShouldHaveValidStrongNames,System.Runtime,#N/A,Secure GetObjectData overrides,"The System.Runtime.Serialization.ISerializable.GetObjectData(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext) method is declared in the ISerializable interface. This interface is implemented by types that provide custom serialization logic. GetObjectData is protected by a security check for System.Security.Permissions.SecurityPermissionAttribute.SerializationFormatter security permission. If an implementation of GetObjectData is not protected by the same security check, callers can call the implementation to bypass security on the interface and gain access to data serialized by the type.",,36,1,0.027777778,56.02689003,Security,,Low,???,,,
  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,,,,
  
negative.code: 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,,,,
  