New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

oss-mariner

Package Overview
Dependencies
Maintainers
3
Versions
16
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

oss-mariner - npm Package Compare versions

Comparing version 0.5.0-beta to 0.5.1-beta

2

dist/src/gitHubIssueFetcher.js

@@ -132,3 +132,3 @@ "use strict";

if (!edge.node.repository) {
console.log(`No repository for ${edge.node.title}`);
tab_level_logger_1.getLogger().info(`\nNo repository for an edge in ${JSON.stringify(variables)}`);
}

@@ -135,0 +135,0 @@ return edge.node.repository;

@@ -8,3 +8,3 @@ "use strict";

const markdownArray = [];
markdownArray.push(`## Updated: ${now.toLocaleString(luxon_1.DateTime.DATETIME_FULL)}`);
markdownArray.push(`## Updated: ${now.toISO()}`);
for (const [dependency, issues] of issuesByDependency) {

@@ -11,0 +11,0 @@ if (!issues || !issues.length) {

{
"name": "oss-mariner",
"version": "0.5.0-beta",
"version": "0.5.1-beta",
"description": "A node.js library for analyzing open source library dependencies",

@@ -5,0 +5,0 @@ "main": "dist/src/mariner/index.js",

@@ -198,2 +198,4 @@ # Mariner

Run `nvm use` to use the appropiate version of Node specified in the .nvmrc file.
Run `npm run build` to compile the code to Javascript.

@@ -226,7 +228,9 @@

1. Update the version number in package.json
1. Be sure the version number in package.json is correct
1. Run `nvm use` to use the appropiate version of Node specified in the .nvmrc file
1. Run `npm install` to update package-lock.json
- Search package-lock.json to be sure there are no references to 'nexus'
1. Run `npm run build` and `npm run lint` to make sure there are no errors
- Make sure package-lock.json has the new version number
1. Run `npm run lint`, then run `npm test`, then run `npm run build` to make sure there are no errors
1. Commit and push the changes, create a PR, have it approved, and merge it into the main branch
1. Switch to main branch and pull the new changes
1. Login to npm if you haven’t already: `npm login`

@@ -236,2 +240,8 @@ 1. Do a dry run to make sure the package looks good: `npm publish --dry-run`

1. Verify that the new version appears at: <https://www.npmjs.com/package/oss-mariner>
1. Create a new GitHub release:
1. On the project homepage, click on `Releases`
1. Click the `Draft a new release` button
1. Enter a release title like `v2.1.3`
1. In the description list the major changes
1. Click the `Publish release` button

@@ -238,0 +248,0 @@ ## Code of Conduct

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