@mlvscan/wasm-core 1.3.2 → 1.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
Binary file
|
|
Binary file
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"mainAssemblyName": "MLVScan.WASM.dll",
|
|
3
3
|
"resources": {
|
|
4
|
-
"hash": "sha256-
|
|
4
|
+
"hash": "sha256-i1D07EwjrXmrAqAxYF7ppEpxfP0CPcD+KZfS+hyDaqg=",
|
|
5
5
|
"jsModuleNative": {
|
|
6
6
|
"dotnet.native.js": "sha256-clxzGaAFwcQ6QWhwQ7dzpD9ktR/87yTache3B45gqoQ="
|
|
7
7
|
},
|
|
@@ -20,8 +20,8 @@
|
|
|
20
20
|
"icudt_no_CJK.dat": "sha256-L7sV7NEYP37/Qr2FPCePo5cJqRgTXRwGHuwF5Q+0Nfs="
|
|
21
21
|
},
|
|
22
22
|
"assembly": {
|
|
23
|
-
"MLVScan.Core.wasm": "sha256-
|
|
24
|
-
"MLVScan.WASM.wasm": "sha256-
|
|
23
|
+
"MLVScan.Core.wasm": "sha256-fvX458bnAiH+CwHUXYj9/+qRmZFzpy3LmXOaM5aoiUw=",
|
|
24
|
+
"MLVScan.WASM.wasm": "sha256-ngcRdQJKo+HOwyvQ0qnC3WnkCZc6Ch36eDxKLUh4Uv0=",
|
|
25
25
|
"Mono.Cecil.wasm": "sha256-Wb+vzfNGLnGGDRhJupS658/i47mVwABGEw9O0N97dlY=",
|
|
26
26
|
"System.Collections.Concurrent.wasm": "sha256-wPVt+aIQOacLbnApfKS4CEzdPtO2romuWNhPI/BrfHw=",
|
|
27
27
|
"System.Collections.wasm": "sha256-TRwwb/PWxTAKfplBNqMkn14z5rNLvuy459MunrnseDo=",
|
package/dist/types.d.ts
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
export { MLVSCAN_SCHEMA_VERSION, } from './generated/mlvscan-schema.js';
|
|
2
2
|
export type { CallChain, CallChainNode, CallChainNodeType, DataFlowChain, DataFlowNode, DataFlowNodeType, DataFlowPattern, DeveloperGuidance, Finding, FindingVisibility, ScanInput, ScanMetadata, ScanMode, ScanPlatform, ScanResult, ScanSummary, SchemaVersion, Severity, ThreatDisposition, ThreatDispositionClassification, ThreatFamily, ThreatFamilyEvidence, ThreatMatchKind, } from './generated/mlvscan-schema.js';
|
|
3
|
+
/**
|
|
4
|
+
* Optional deep-analysis controls accepted by {@link ScanConfigInput.deepAnalysis}.
|
|
5
|
+
*
|
|
6
|
+
* These settings expose the same high-cost analysis toggles used by MLVScan.Core.
|
|
7
|
+
* Most browser integrations should leave them unset and rely on the default quick-scan profile.
|
|
8
|
+
*/
|
|
3
9
|
export interface DeepBehaviorAnalysisConfig {
|
|
4
10
|
enableDeepAnalysis?: boolean;
|
|
5
11
|
emitDiagnosticFindings?: boolean;
|
|
@@ -18,6 +24,12 @@ export interface DeepBehaviorAnalysisConfig {
|
|
|
18
24
|
maxDeepMethodsPerAssembly?: number;
|
|
19
25
|
maxTrackedDataFlowEdgesPerMethod?: number;
|
|
20
26
|
}
|
|
27
|
+
/**
|
|
28
|
+
* Browser-facing scan configuration passed to `scanAssemblyWithConfig`.
|
|
29
|
+
*
|
|
30
|
+
* This mirrors the public Core scan options while keeping the shape friendly for JSON serialization.
|
|
31
|
+
* Omitted values use the WASM scanner defaults.
|
|
32
|
+
*/
|
|
21
33
|
export interface ScanConfigInput {
|
|
22
34
|
developerMode?: boolean;
|
|
23
35
|
enableCrossMethodAnalysis?: boolean;
|