codecov-io
commented
5 years ago Codecov Report
Merging #70 into development will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## development #70 +/- ##
==========================================
Coverage 100% 100%
==========================================
Files 267 267
Lines 2208 2208
Branches 222 222
==========================================
Hits 2208 2208Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update b2c1876...19e04b2. Read the comment docs.
Bumps ssri from 5.2.1 to 5.3.0. This update includes security fixes.
Vulnerabilities fixed
*Sourced from [The Sonatype OSS Index](https://ossindex.sonatype.org/vuln/bc171f6c-7dcb-4fd9-ac33-69690811c662).* > **CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion')** > The software does not properly restrict the size or amount of resources that are requested or influenced by an actor, which can be used to consume more resources than intended. > > Affected versions: <=5.2.1 *Sourced from The GitHub Security Advisory Database.* > **Moderate severity vulnerability that affects ssri** > index.js in the ssri module before 5.2.2 for Node.js is prone to a regular expression denial of service vulnerability in strict mode functionality via a long base64 hash string. > > Affected versions: < 5.2.2Changelog
*Sourced from [ssri's changelog](https://github.com/zkat/ssri/blob/latest/CHANGELOG.md).* > # [5.3.0](https://github.com/zkat/ssri/compare/v5.2.4...v5.3.0) (2018-03-13) > > > ### Features > > * **checkData:** optionally throw when checkData fails ([bf26b84](https://github.com/zkat/ssri/commit/bf26b84)) > > > > > ## [5.2.4](https://github.com/zkat/ssri/compare/v5.2.3...v5.2.4) (2018-02-16) > > > > > ## [5.2.3](https://github.com/zkat/ssri/compare/v5.2.2...v5.2.3) (2018-02-16) > > > ### Bug Fixes > > * **hashes:** filter hash priority list by available hashes ([2fa30b8](https://github.com/zkat/ssri/commit/2fa30b8)) > * **integrityStream:** dedupe algorithms to generate ([d56c654](https://github.com/zkat/ssri/commit/d56c654)) > > > > > ## [5.2.2](https://github.com/zkat/ssri/compare/v5.2.1...v5.2.2) (2018-02-14) > > > ### Bug Fixes > > * **security:** tweak strict SRI regex ([#10](https://github-redirect.dependabot.com/zkat/ssri/issues/10)) ([d0ebcdc](https://github.com/zkat/ssri/commit/d0ebcdc)) > > > >Commits
- [`0ae0c23`](https://github.com/zkat/ssri/commit/0ae0c237690d0b33613524a318ec617b8a61f8b0) chore(release): 5.3.0 - [`bf26b84`](https://github.com/zkat/ssri/commit/bf26b842be775faf2961ac76355e9eecf262ed5a) feat(checkData): optionally throw when checkData fails - [`d0f7429`](https://github.com/zkat/ssri/commit/d0f7429cb8d5c38a3aab1dde24a725c61fe2d69d) chore(release): 5.2.4 - [`38878b7`](https://github.com/zkat/ssri/commit/38878b72be22161c54fb00748e0f74464e916455) docs: integrityStream docs were wrong - [`5e6fcee`](https://github.com/zkat/ssri/commit/5e6fcee066a60e2a7dc505dc1912c0502844e39d) chore(release): 5.2.3 - [`58b8cfe`](https://github.com/zkat/ssri/commit/58b8cfe43a1fcd6f8ca4a42e875c59303c581946) test: use strict for test/create.js - [`2fa30b8`](https://github.com/zkat/ssri/commit/2fa30b8aba9e1fa24782629e6f2c0e9121603c43) fix(hashes): filter hash priority list by available hashes - [`d56c654`](https://github.com/zkat/ssri/commit/d56c6541c6dff9ae68267925ddd11e6590389a48) fix(integrityStream): dedupe algorithms to generate - [`e3845d5`](https://github.com/zkat/ssri/commit/e3845d53990f31aec9eea898d4e909f6f0b1691f) test: add tests for integrity-stream - [`0fb45e7`](https://github.com/zkat/ssri/commit/0fb45e7e0eba615bf0080bf350c95e19412ff9a9) chore(release): 5.2.2 - Additional commits viewable in [compare view](https://github.com/zkat/ssri/compare/v5.2.1...v5.3.0)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.