You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
throw new ERR_SRI_PARSE(str, str[prevIndex], prevIndex);
402
-
^
403
-
404
-
SyntaxError [ERR_SRI_PARSE]: Subresource Integrity string "sha256-iuGZ6SFVFpMuHUcJciQTIKpIyaQVigMZlvg9Lx66HV8=%" had an unexpected "%" at position 51
405
-
at new NodeError (node:internal/errors:393:5)
406
-
at Object.parse (node:internal/policy/sri:65:13)
407
-
at processEntry (node:internal/policy/manifest:581:38)
408
-
at Manifest.assertIntegrity (node:internal/policy/manifest:588:32)
409
-
at Module._compile (node:internal/modules/cjs/loader:1119:21)
410
-
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
411
-
at Module.load (node:internal/modules/cjs/loader:1037:32)
412
-
at Module._load (node:internal/modules/cjs/loader:878:12)
413
-
at Module.require (node:internal/modules/cjs/loader:1061:19)
414
-
at require (node:internal/modules/cjs/helpers:99:18) {
415
-
code: 'ERR_SRI_PARSE'
416
-
}
417
-
```
429
+
- File system reads and writes.
430
+
- Network access (inbound and outbound).
431
+
- Child process creation.
432
+
- Use of native addons and other powerful APIs.
433
+
434
+
This can help contain the impact of malicious or compromised dependencies,
435
+
untrusted configuration, or unexpected behavior in your own code, since even
436
+
trusted code will be prevented from performing actions outside the permissions
437
+
you have explicitly granted.
418
438
419
-
Note, it's always recommended the use of `--policy-integrity` to avoid policy mutations.
439
+
Refer to the [Node.js permissions documentation][] for up-to-date flags and
440
+
options.
420
441
421
442
## Experimental Features in Production
422
443
@@ -431,6 +452,8 @@ The [OpenSSF][] is leading several initiatives that can be very useful, especial
431
452
-[OpenSSF Scorecard][] Scorecard evaluates open source projects using a series of automated security risk checks. You can use it to proactively assess vulnerabilities and dependencies in your code base and make informed decisions about accepting vulnerabilities.
432
453
-[OpenSSF Best Practices Badge Program][] Projects can voluntarily self-certify by describing how they comply with each best practice. This will generate a badge that can be added to the project.
433
454
455
+
You can also collaborate with other projects and security experts through the [OpenJS Security Collaboration Space][].
0 commit comments