Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

echidna-manifester

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

echidna-manifester

Load a file you give to it (local or URL) and list all linked resources

  • 0.1.0
  • latest
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

echidna-manifester

Some people (whose names shall remain a secret) complained that it could be too hard to generate Echidna manifests.

What this tool does is load a file you give to it (local or URL) and try to list all the resources that it loads, and that are situated under the same directory as that file.

In theory, if you've done things well (and your document can be published under TR without modification), then this should list all the dependencies you have that should go into your Echidna manifest. You can paste them there.

Warnings

There are good reasons that this is not supported directly by Echidna. In the general case, if you had a reliable process to detect all the resources that a Web page might load then you would have a solution to the Halting Problem.

So keep in mind that this isn't perfect. For instance, if your document loads stuff that causes other stuff to be loaded by script over time, it's possible that the process will time out before some resources are loaded, and so they won't get loaded. For specs that should not happen, but for instance if ReSpec+PhantomJS are being slow together you could be out of luck.

This also does not generate the first entry (the main document) because it can't guess all the parameters for that. Presumably that's not too bad a problem.

Installation

To use it from the command line, type:

$ npm install -g echidna-manifester

To use as a Node.js module, add it to your package.json file:

"dependencies": {
    ⋮
    "echidna-manifest": "^0.1.0"
}

And require it as usual:

var em = require('echidna-manifester');

Usage

From the command line, invoke it with these arguments:

$ echidna-manifester <PATH/TO/FILE> [OPTIONS-AS-JSON]

Some examples:

$ echidna-manifester http://berjon.com/
$ echidna-manifester /tmp/spec.html '{"format": "plain"}'
$ echidna-manifester https://foo.com/bar.html '{"includeErrors": true, "includeTypes": true}'

As a Node.js module: echidna-manifester exports only one function, run. These are its arguments:

  1. url (String): required
  2. options (Object): optional.
    If absent, default options will be applied.
  3. callback (Function): optional.
    Signature: function(data).
    If absent, the output will be console.logged.
var em = require('echidna-manifester');
var url = 'https://foo.com/bar.html';
var options = {
    "format": "json",
    "compactUrls": false,
};
var callback = function(data) {
    console.dir(data);
};

em.run(url, options, callback);

Output formats and options

The object options may include these properties (default values are in bold):

  • 'format':
    {'manifest', 'json', 'plain'}
    • 'manifest': a format that is appropriate for an Echidna manifest
    • 'json': a JSON object
    • 'plain': text, one line per resource, fields separated by spaces: URL STATUS [TYPE]
  • 'compactUrls'
    {true, false}
    Omit the beginning of the URL
  • 'includeErrors'
    {true, false}
    Whether resources that could not be loaded should be included in the output, too
  • 'includeTypes'
    {true, false}
    Add a string to idenfity the type of resource (kind of MIME), if possible;
    this parameter is ignored when the format is 'manifest'

Examples

All these examples use this dummy spec:
http://www.w3.org/People/Antonio/spec/dummy-spec.html

Use from the command line, with default options:

$ node echidna-manifester http://www.w3.org/People/Antonio/spec/dummy-spec.html
dummy-spec.html
foo.css
baz.js
http://www.w3.org/Consortium/Offices/w3coffice.png
http://www.w3.org/2014/10/stdvidthumb.png
bar.jpeg

Invoke from JavaScript, specifying JSON output and failed resources too:

var em = require('echidna-manifester');

em.run(
    'http://www.w3.org/People/Antonio/spec/dummy-spec.html',
    {
        "format":        "json",
        "includeErrors": true
    },
    processJSON
);
{
    "ok": [
        {"url": "dummy-spec.html"},
        {"url": "foo.css"},
        {"url": "baz.js"},
        {"url": "http://www.w3.org/Consortium/Offices/w3coffice.png"},
        {"url": "http://www.w3.org/2014/10/stdvidthumb.png"},
        {"url": "bar.jpeg"}
    ],
    "error": [
        {"url": "i-do-not-exist.css"},
        {"url": "i-do-not-exist.svg"}
    ]
}

From the command line, in plain text, with full URLs and with types:

$ node echidna-manifester http://www.w3.org/People/Antonio/spec/dummy-spec.html '{"format": "plain", "includeTypes": true, "compactUrls": false}'
http://www.w3.org/People/Antonio/spec/dummy-spec.html ok html
http://www.w3.org/People/Antonio/spec/foo.css ok css
http://www.w3.org/People/Antonio/spec/baz.js ok js
http://www.w3.org/Consortium/Offices/w3coffice.png ok img
http://www.w3.org/2014/10/stdvidthumb.png ok img
http://www.w3.org/People/Antonio/spec/bar.jpeg ok img

Keywords

FAQs

Package last updated on 28 Aug 2015

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc