webtorrent / magnet-uri Goto Github PK

Please open-source https://checker.openwebtorrent.com

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.0.1 of standard was just published.

This version is covered by your current version range and after updating it in your project the build failed.

standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 11.0.0 of standard was just published.

This version is covered by your current version range and after updating it in your project the build failed.

standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

encodeURIComponent causing an exception if the function argument contains Unicode symbols

URIError: URI malformed
at encodeURIComponent (native)
at /home/nodejsuser/offcloud/server/downloader/node_modules/parse-torrent/node_modules/magnet-uri/index.js:117:17
at Array.forEach (native)
at /home/nodejsuser/offcloud/server/downloader/node_modules/parse-torrent/node_modules/magnet-uri/index.js:112:14
at Array.forEach (native)
at Function.magnetURIEncode as toMagnetURI

I think it makes sense to filter/escape value before encodeURIComponent, or catch the exception

Although some consider the (acceptable source) as= for web seeding source, the parameter ws= should be used as url-list counterpart in magnet case.

I think its not a big change.

Some references

Transmission magnet parser:
https://trac.transmissionbt.com/browser/trunk/libtransmission/magnet.c#L169

French wikipedia (OK, maybe not THE source)
http://fr.wikipedia.org/wiki/Magnet_(standard)

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

If a parsed torrent has repeated trackers the encoder will allow it and add them repeatedly

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency uint8-util to ^2.2.5
• chore(deps): update dependency semantic-release to v24

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: author, Invalid configuration option: bugs, Invalid configuration option: funding, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: main, Invalid configuration option: name, Invalid configuration option: packageRules[0].bep53-range, Invalid configuration option: packageRules[0].thirty-two, Invalid configuration option: packageRules[1].standard, Invalid configuration option: packageRules[1].tape, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version

As of d85461b, module breaks on Node 4. Maybe use safe-buffer for better compatibility?

Version 4.9.0 of tape was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴