
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Check your provider API implementation for a Modulus add-on quickly and easily.
Install using $ [sudo] npm install -g dia
Implement your add-on provider API following the instructions found in the
Modulus codex or start with the
example add-on project here.
Once your API is implemented, start your server up at the base test URL
configured in your manifest and run $ dia test
with your manifest (either from
the working directory that contains the manifest or use the -f
option).
Run all tests for your add-on by running $ dia test
or test individual
endpoints (see below). Use the -f
option to specify the location of the
manifest for your add-on; otherwise, the current working directory will be used.
Note: the provided manifest will be validated for each check
Failed checks will provide a description of what is missing or incorrect. Once all checks pass, submit your add-on to Modulus.
Run $ dia -h
for a complete list of commands and options.
Usage: dia [options] [command]
Commands:
init initialize a skeleton manifest
test run all add-on tests
test manifest test a manifest (run before each test)
test provision [params] simulate a provision call
test deprovision <id> simulate a deprovision call
test planchange <id> [new_plan] simulate a plan change
test sso <id> simulate single sign on authentication for the add-on with the specified ID
Options:
-h, --help output usage information
-V, --version output the version number
-f, --filename <path> path to manifest.json file - defaults to the current working directory
-p, --plan <plan> provision the specified plan instead of "test"
The MIT License (MIT)
Copyright (c) 2013 Modulus
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Modulus add-on test utility.
The npm package dia receives a total of 4 weekly downloads. As such, dia popularity was classified as not popular.
We found that dia demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.