Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade graphql-tag from 2.11.0 to 2.12.1 #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade graphql-tag from 2.11.0 to 2.12.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2021-02-12.
Release notes
Package name: graphql-tag
  • 2.12.1 - 2021-02-12

    Bump npm version to 2.12.1.

  • 2.12.0 - 2021-01-29

    Bump npm version to 2.12.0.

  • 2.11.0 - 2020-07-28
    • package.json sideEffects changes to clearly identify that graphql-tag doesn't have side effects.
      @ hwillson in #313
from graphql-tag GitHub release notes
Commit messages
Package name: graphql-tag

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@mistaken-pull-closer
Copy link

Thanks for your submission.

It appears that you've created a pull request using one of our repository's branches. Since this is
almost always a mistake, we're going to go ahead and close this. If it was intentional, please
let us know what you were intending and we can see about reopening it.

Thanks again!

@mistaken-pull-closer mistaken-pull-closer bot added the invalid This doesn't seem right label Mar 28, 2021
@pull-dog
Copy link

pull-dog bot commented Mar 28, 2021

*Ruff* 🐶 The test environment for this pull request has been destroyed 💥 This may have happened explicitly via a command, because the environment expired, or because the pull request was closed.

What is this?

Pull Dog is a GitHub app that makes test environments for your pull requests using Docker, from a docker-compose.yml file you specify. It takes 19 seconds to set up (we counted!) and there's a free plan available.

Visit our website to learn more.

Commands
  • @pull-dog up to reprovision or provision the server.
  • @pull-dog down to delete the provisioned server.
Troubleshooting

Need help? Don't hesitate to file an issue in our repository

Configuration

{
  "isLazy": false,
  "dockerComposeYmlFilePaths": [
    "docker-compose.yml"
  ],
  "expiry": "00:00:00",
  "conversationMode": "singleComment"
}

Trace ID
No trace ID

@guardrails
Copy link

guardrails bot commented Mar 28, 2021

⚠️ We detected security issues in this pull request:
Mode: paranoid | Total findings: 82 | Considered vulnerability: 0

Hard-Coded Secrets (16)

this.clusterSecret = clusterSecret;

const secret = process.env.PRISMA_MANAGEMENT_API_SECRET || this.clusterSecret;

clusterSecret: this.clusterSecret,


clusterSecret: cluster.clusterSecret,






fs.writeFileSync(envPath, `MY_DOT_ENV_SECRET=this-is-very-secret,and-comma,seperated`);





apiKey: '811d453fc7f80306044dd5cc4b87e064',

More info on how to fix Hard-Coded Secrets in General.


Insecure Use of Dangerous Function (12)

const tsconfig = require(TSCONFIG);

const { execSync } = require('child_process');

const packageJsonContent = require(path.join(__dirname, '..', packageJsonPath));

const cp = require('child_process');

const pkg = require(pkgPath);

const extractExports = execOptions.extractExports || DEFAULT_EXTRACT_EXPORTS_FACTORY(execOptions.exportNames);

if (options && options.require) {



const asyncImport: AsyncImportFn = (moduleName: string) => import(moduleName);

const filePath = './fixtures/test.graphql';

// eslint-disable-next-line no-eval

More info on how to fix Insecure Use of Dangerous Function in Javascript and Typescript.


Insecure File Management (33)

const contents = await fsPromises.readFile(filePath, 'utf-8');

await fsPromises.writeFile(filePath, contentsTrimmed);

const lsStat = await fsPromises.lstat(filePath);

const filesInDirectory = await fsPromises.readdir(filePath);

const ifExists = await fsPromises

const oldContent = fs.readFileSync(filePath, 'utf-8');

await fsPromises.writeFile(filePath, finalContent);

fs.writeFileSync(

const filesInDirectory = fs.readdirSync(dirName);

const fileLstat = fs.lstatSync(absoluteFilePath);

const moduleDir = 'node_modules/graphql-import-test';

if (!fs.existsSync(moduleDir)) {


fs.writeFileSync(moduleDir + '/b.graphql', b);


this.rcPath = path.join(this.home, '.prisma/config.yml');

const rcString = yaml.dump(JSON.parse(JSON.stringify(rc)));





fs.mkdirSync(path.dirname(envPath), { recursive: true });




fs.mkdirSync(path.dirname(envPath), { recursive: true });




this.definitionString = replaceYamlValue(this.definitionString, 'endpoint', newEndpoint);

this.definitionString += `\ndatamodel: ${datamodel}`;

const dir = path.join(os.tmpdir(), cuid() + '/');

More info on how to fix Insecure File Management in Javascript and Typescript.


Insecure Use of Crypto (13)


reviews: (user) => reviews.filter(review => review.authorId === user.id),



token.line + 1 === token.next.line &&


reviews: (user) => reviews.filter(review => review.authorId === user.id),


type: new GraphQLList(reviewsSchemaTypes.Review),


reviews: (user) => reviews.filter(review => review.authorId === user.id),


token.line + 1 === token.next.line &&

More info on how to fix Insecure Use of Crypto in Typescript.


Insecure Access Control (5)

return function next() {


if (isSchemaVisitor(visitorOrVisitorDef)) {

field.args.forEach(arg => {

More info on how to fix Insecure Access Control in Typescript.


Insecure Use of Regular Expressions (3)



More info on how to fix Insecure Use of Regular Expressions in Typescript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment