gulp-mraudit 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,11 @@
1
+ {
2
+ "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
3
+ "changelog": ["@changesets/changelog-github", { "repo": "lirantal/gulp-mraudit" }],
4
+ "commit": false,
5
+ "fixed": [],
6
+ "linked": [],
7
+ "access": "public",
8
+ "baseBranch": "master",
9
+ "updateInternalDependencies": "patch",
10
+ "ignore": []
11
+ }
@@ -0,0 +1,9 @@
1
+ default: true
2
+
3
+ # Line length - https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md013---line-length
4
+ MD013:
5
+ code_blocks: false
6
+ tables: false
7
+
8
+ # Do not enforce line length in markdown files
9
+ line_length: false
@@ -0,0 +1,73 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ education, socio-economic status, nationality, personal appearance, race,
10
+ religion, or sexual identity and orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ - Using welcoming and inclusive language
18
+ - Being respectful of differing viewpoints and experiences
19
+ - Gracefully accepting constructive criticism
20
+ - Focusing on what is best for the community
21
+ - Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ - The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ - Trolling, insulting/derogatory comments, and personal or political attacks
28
+ - Public or private harassment
29
+ - Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ - Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at liran.tal@gmail.com. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/
72
+
73
+ [homepage]: https://www.contributor-covenant.org
@@ -0,0 +1,56 @@
1
+ version: 2
2
+ updates:
3
+ - package-ecosystem: "github-actions"
4
+ directory: ".github/workflows"
5
+ schedule:
6
+ interval: "monthly"
7
+ commit-message:
8
+ # Prefix all commit messages with "chore: "
9
+ prefix: "chore"
10
+ open-pull-requests-limit: 10
11
+ cooldown:
12
+ default-days: 30
13
+ # Use the 'dependencies' default label and add
14
+ # the 'automerge' one for automerge github action support
15
+ labels:
16
+ - "dependencies"
17
+ - "automerge"
18
+
19
+ - package-ecosystem: "npm"
20
+ directory: "/"
21
+ commit-message:
22
+ # Prefix all commit messages with "chore: "
23
+ prefix: "chore"
24
+ schedule:
25
+ interval: "weekly"
26
+ open-pull-requests-limit: 10
27
+ cooldown:
28
+ default-days: 30
29
+ semver-major-days: 30
30
+ semver-minor-days: 30
31
+ semver-patch-days: 30
32
+ # Use the 'dependencies' default label and add
33
+ # the 'automerge' one for automerge github action support
34
+ labels:
35
+ - "dependencies"
36
+ - "automerge"
37
+ groups:
38
+ # Production dependencies without breaking changes
39
+ dependencies:
40
+ dependency-type: "production"
41
+ update-types:
42
+ - "minor"
43
+ - "patch"
44
+ # Production dependencies with breaking changes
45
+ dependencies-major:
46
+ dependency-type: "production"
47
+ update-types:
48
+ - "major"
49
+ # Development dependencies
50
+ dev-dependencies:
51
+ dependency-type: "development"
52
+ # example for ignoring dependencies:
53
+ # ignore:
54
+ # - dependency-name: tap
55
+ # update-types: ["version-update:semver-major"]
56
+
@@ -0,0 +1,20 @@
1
+ documentation:
2
+ - changed-files:
3
+ - any-glob-to-any-file:
4
+ - "docs/*"
5
+ - "**/*.md"
6
+ - "guides/*"
7
+
8
+ build:
9
+ - changed-files:
10
+ - any-glob-to-any-file: ".github/workflows/*"
11
+
12
+ typescript:
13
+ - changed-files:
14
+ - any-glob-to-any-file: "**/*[.|-]d.ts"
15
+
16
+ cli:
17
+ - any: ["bin/**/*", "cli/**/*"]
18
+
19
+ test:
20
+ - any: ["test/**/*", "__tests__/**/*"]
@@ -0,0 +1,39 @@
1
+ name: automerge
2
+
3
+ on:
4
+ pull_request:
5
+ types:
6
+ - labeled
7
+ - unlabeled
8
+ - synchronize
9
+ - opened
10
+ - edited
11
+ - ready_for_review
12
+ - reopened
13
+ check_run:
14
+ types:
15
+ - completed
16
+ status: {}
17
+
18
+ permissions: {} # deny-all at workflow level; each job declares only what it needs
19
+
20
+ jobs:
21
+ automerge:
22
+ name: Automerge
23
+ runs-on: ubuntu-latest
24
+ if: github.event_name != 'check_run' || github.event.check_run.name != 'Automerge'
25
+ permissions:
26
+ contents: write
27
+ pull-requests: write
28
+ checks: read
29
+ statuses: read
30
+ steps:
31
+ - name: Merge eligible pull requests
32
+ uses: lirantal/github-action-automerge@8ea9b60ae1fe716a5128fefa26f3df1ba8417742 # 1.0.1
33
+ with:
34
+ label: automerge
35
+ merge-method: squash
36
+ green-observations-required: "4"
37
+ poll-interval-seconds: "60"
38
+ timeout-seconds: "3600"
39
+ ignored-check-names: Automerge
@@ -0,0 +1,38 @@
1
+ name: CI
2
+
3
+ on: [push, pull_request]
4
+
5
+ permissions: {}
6
+
7
+ jobs:
8
+ test:
9
+ permissions:
10
+ contents: read
11
+ strategy:
12
+ matrix:
13
+ node: ["24.x"]
14
+ platform: [ubuntu-latest]
15
+ name: Node v${{matrix.node}} ((${{matrix.platform}}))
16
+ runs-on: ${{matrix.platform}}
17
+ steps:
18
+ - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
19
+ - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
20
+ with:
21
+ node-version: ${{matrix.node}}
22
+ - name: install dependencies
23
+ run: npm install --ignore-scripts --legacy-peer-deps --engine-strict=false --allow-git=true
24
+ - name: lint code
25
+ run: npm run lint
26
+ - name: build project
27
+ run: npm run build
28
+ - name: run tests
29
+ run: npm run test
30
+ - name: coverage
31
+ uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f # v7.0.0
32
+ if: github.actor != 'dependabot[bot]'
33
+ with:
34
+ fail_ci_if_error: false
35
+ verbose: false
36
+ token: ${{ secrets.CODECOV_TOKEN }}
37
+ env:
38
+ CI: true
@@ -0,0 +1,14 @@
1
+ name: "Pull Request Labeler"
2
+
3
+ on: pull_request
4
+
5
+ permissions: {}
6
+
7
+ jobs:
8
+ label:
9
+ permissions:
10
+ contents: read
11
+ pull-requests: write
12
+ runs-on: ubuntu-latest
13
+ steps:
14
+ - uses: actions/labeler@f27b608878404679385c85cfa523b85ccb86e213 # v6.1.0
@@ -0,0 +1,43 @@
1
+ name: Links Checker (Lychee, On Schedule)
2
+
3
+ on:
4
+ repository_dispatch:
5
+ workflow_dispatch:
6
+ schedule:
7
+ - cron: "00 18 * * *"
8
+
9
+ permissions: {}
10
+
11
+ jobs:
12
+ linkChecker:
13
+ permissions:
14
+ contents: read
15
+ issues: write
16
+ runs-on: ubuntu-latest
17
+ steps:
18
+ - name: Check out repo
19
+ uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
20
+ with:
21
+ persist-credentials: false
22
+
23
+ - name: Restore lychee cache
24
+ uses: actions/cache@v4
25
+ with:
26
+ path: .lycheecache
27
+ key: cache-lychee-${{ github.sha }}
28
+ restore-keys: cache-lychee-
29
+
30
+ - name: Link Checker
31
+ id: lychee
32
+ uses: lycheeverse/lychee-action@e7477775783ea5526144ba13e8db5eec57747ce8 # v2.9.0
33
+ with:
34
+ args: --root-dir "$(pwd)" --cache --max-cache-age 1d . --max-retries 5 --retry-wait-time 60 --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36" --remap '.*npmjs\.org/package/(.*) https://registry.npmjs.com/$1' --remap '.*npmjs\.com/package/(.*) https://registry.npmjs.com/$1' --max-concurrency 1 -vv
35
+ fail: false
36
+
37
+ - name: Create Issue From File
38
+ if: steps.lychee.outputs.exit_code != 0
39
+ uses: peter-evans/create-issue-from-file@fca9117c27cdc29c6c4db3b86c48e4115a786710 # v6.0.0
40
+ with:
41
+ title: Link Checker Report (lycheeverse/lychee-action)
42
+ content-filepath: ./lychee/out.md
43
+ labels: report, automated issue
@@ -0,0 +1,34 @@
1
+ ---
2
+ name: stale
3
+
4
+ on:
5
+ workflow_dispatch:
6
+ schedule:
7
+ - cron: "9 9 * * *"
8
+
9
+ permissions:
10
+ issues: write
11
+ pull-requests: write
12
+
13
+ jobs:
14
+ stale:
15
+ runs-on: ubuntu-latest
16
+ steps:
17
+ - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10.3.0
18
+ with:
19
+ close-issue-message: |
20
+ This issue has not seen any activity since it was marked stale.
21
+ Closing.
22
+ close-pr-message: |
23
+ This pull request has not seen any activity since it was marked stale.
24
+ Closing.
25
+ exempt-issue-labels: good-first-issue,need-help,no-stale,pinned,security
26
+ exempt-pr-labels: "autorelease: pending,good-first-issue,need-help,no-stale,pinned,security"
27
+ stale-issue-label: stale
28
+ stale-issue-message: |
29
+ This issue is stale because it has been open 60 days with no activity.
30
+ Remove stale label or comment or this will be closed in 7 days
31
+ stale-pr-label: stale
32
+ stale-pr-message: |
33
+ This PR is stale because it has been open 60 days with no activity.
34
+ Remove stale label or comment or this will be closed in 7 days.
@@ -0,0 +1,29 @@
1
+ name: Markdown Lint
2
+
3
+ on:
4
+ push:
5
+ branches:
6
+ - master
7
+ pull_request:
8
+
9
+ permissions: {}
10
+
11
+ jobs:
12
+ markdown_lint:
13
+ permissions:
14
+ contents: read
15
+ name: Lint Markdown files
16
+ runs-on: ubuntu-latest
17
+ steps:
18
+ - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
19
+
20
+ - name: Setup Node.js
21
+ uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
22
+ with:
23
+ node-version: '24.x'
24
+
25
+ - name: Install dependencies
26
+ run: npm install --ignore-scripts --legacy-peer-deps --engine-strict=false --allow-git=true
27
+
28
+ - name: Markdown Lint
29
+ run: npm run lint:markdown || true
@@ -0,0 +1,40 @@
1
+ name: release
2
+
3
+ on:
4
+ push:
5
+ branches:
6
+ - master
7
+
8
+ concurrency: ${{ github.workflow }}-${{ github.ref }}
9
+
10
+ permissions: {}
11
+
12
+ jobs:
13
+ release:
14
+ permissions:
15
+ contents: write # to create release (changesets/action)
16
+ issues: write # to post issue comments (changesets/action)
17
+ pull-requests: write # to create pull request (changesets/action)
18
+ id-token: write # to create release (changesets/action)
19
+ packages: write # to publish to npm (changesets/action)
20
+ timeout-minutes: 20
21
+ runs-on: ubuntu-latest
22
+ steps:
23
+ - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
24
+ - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
25
+ with:
26
+ node-version: 24.x
27
+ - name: install dependencies
28
+ run: npm install --ignore-scripts --legacy-peer-deps --engine-strict=false --allow-git=true
29
+ - name: build project
30
+ run: npm run build
31
+ - name: Create Release Pull Request or Publish to npm
32
+ uses: changesets/action@a45c4d594aa4e2c509dc14a9f2b3b67ba3780d0d # v1.9.0
33
+ with:
34
+ publish: npm run release
35
+ version: npm run version
36
+ commit: "chore: new release"
37
+ title: "chore: new release candidate"
38
+ env:
39
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
40
+ NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
@@ -0,0 +1,37 @@
1
+ name: Repository init
2
+
3
+ on:
4
+ workflow_dispatch:
5
+ push:
6
+ branches: [master]
7
+ paths:
8
+ - '.github/workflows/repo-init.yml' # only fires when this file itself changes
9
+ schedule:
10
+ - cron: '0 9 * * 1' # Every Monday at 09:00 UTC
11
+
12
+ permissions: {} # deny-all at workflow level; each job declares only what it needs
13
+
14
+ jobs:
15
+ create-label:
16
+ runs-on: ubuntu-latest
17
+ permissions:
18
+ issues: write
19
+ steps:
20
+ - name: Create automerge label
21
+ env:
22
+ GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
23
+ run: |
24
+ gh label create "automerge" \
25
+ --repo "${{ github.repository }}" \
26
+ --color "0075ca" \
27
+ --description "Merge this PR automatically once checks pass" \
28
+ --force
29
+ - name: Create dependencies label
30
+ env:
31
+ GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
32
+ run: |
33
+ gh label create "dependencies" \
34
+ --repo "${{ github.repository }}" \
35
+ --color "0366d6" \
36
+ --description "Pull requests that update a dependency" \
37
+ --force
@@ -0,0 +1,16 @@
1
+ __tests__
2
+ .git
3
+ .github
4
+ .changeset
5
+ CODE_OF_CONDUCT.md
6
+ CHANGELOG.md
7
+ docs/**
8
+ __template__
9
+ __template__draft_/**
10
+ node_modules
11
+ dist
12
+ README.md
13
+ DESIGN.md
14
+ plugin/markdown/**
15
+ plugin/**
16
+ demo/**
@@ -0,0 +1,102 @@
1
+ # Contributing
2
+
3
+ Thanks for taking the time to contribute! Issues, ideas, and PRs are all welcome.
4
+ The notes below are guidelines to help your contribution land smoothly. If in doubt, open the thing anyway and we'll figure it out together.
5
+
6
+ ## Opening an issue
7
+
8
+ A good issue gives us enough to reproduce or understand the ask. Useful things to include:
9
+
10
+ - **For bugs:** what you expected, what actually happened, and the shortest repro you can manage. Versions (runtime, OS, package) and stack traces help.
11
+ - **For features:** the problem you're trying to solve, not just the solution you have in mind. A concrete example of how you'd use it is gold.
12
+
13
+ A quick search of existing issues helps avoid duplicates, but don't agonize over it.
14
+
15
+ ## Proposing a PR
16
+
17
+ PRs are expected to meet a few baseline requirements before review:
18
+
19
+ - **Tests are required** for any behavior change, new features need new tests, bug fixes need a regression test that fails without the fix.
20
+ - **Existing tests must pass** locally and in CI. Don't disable or skip tests to make a PR green.
21
+ - **Coverage should not regress.** If your change drops coverage meaningfully, add tests or explain why in the PR description.
22
+ - **Linters and type checks must pass.** Run them locally before pushing; CI will reject otherwise.
23
+ - **One logical change per PR.** Refactors, formatting churn, and unrelated fixes belong in separate PRs, it makes review and revert sane.
24
+ - **Describe what and why.** A PR title and a few lines of context go a long way, reviewers shouldn't have to reverse-engineer your intent from the diff.
25
+ - **Link the issue you're closing.** If your PR resolves an open issue, include a `Related issues` section in the description with `Fixes: #<issue-number>` so GitHub auto-closes it on merge.
26
+ - **Breaking changes need a heads-up** in the PR description, plus a migration note for users.
27
+
28
+ Large or speculative changes: open an issue first to align on direction before investing time.
29
+
30
+ ## Changesets
31
+
32
+ This package is released with Changesets. Any PR that changes published package behavior must include a changeset so the release PR can include the right version bump and changelog entry.
33
+
34
+ Add a patch changeset for:
35
+
36
+ - Bug fixes that affect CLI/runtime behavior.
37
+ - New or changed CLI flags, commands, output, or errors.
38
+ - Documentation changes that accompany a user-facing behavior change.
39
+
40
+ A changeset is usually not needed for:
41
+
42
+ - Tests only.
43
+ - Refactors with no behavior change.
44
+ - CI/tooling-only changes.
45
+ - Documentation-only changes that do not describe a new release-worthy behavior.
46
+
47
+ Before opening a PR, check whether the change affects the published npm package. If yes, create a patch changeset unless the maintainer explicitly says not to. When in doubt, add a patch changeset.
48
+
49
+ ## Commit guidelines
50
+
51
+ This project follows [Conventional Commits](https://www.conventionalcommits.org/). The format is:
52
+
53
+ ```text
54
+ <type>(<optional scope>): <short summary>
55
+ ```
56
+
57
+ Common types:
58
+
59
+ - `feat:` — a new feature
60
+ - `fix:` — a bug fix
61
+ - `docs:` — documentation only
62
+ - `refactor:` — code change that neither fixes a bug nor adds a feature
63
+ - `test:` — adding or fixing tests
64
+ - `chore:` — tooling, build, dependencies
65
+ - `perf:` — performance improvement
66
+
67
+ Examples:
68
+
69
+ ```text
70
+ feat: support multiple input files
71
+ fix(parser): handle empty input gracefully
72
+ docs: clarify install instructions
73
+ ```
74
+
75
+ Breaking changes: add `!` after the type (`feat!: ...`) and explain the break in the commit body.
76
+
77
+ This format drives changelog generation and release automation, so it matters more than the average commit-style guide.
78
+
79
+ ## Local development
80
+
81
+ 1. Fork and clone the repository.
82
+ 2. Install dependencies using the project's package manager (see `package.json`, or equivalent).
83
+ 3. Run the test suite to confirm a clean baseline before making changes.
84
+ 4. Run the linter and type checker (if configured) the same way.
85
+ 5. Make your change on a feature branch, commit using the format above, and open a PR.
86
+
87
+ If any of the above doesn't work on a fresh checkout, that's a bug, please open an issue.
88
+
89
+ ## For automated agents
90
+
91
+ ### Environment setup
92
+
93
+
94
+ ### Release readiness
95
+
96
+ Before opening a PR, automated agents must check the [Changesets](#changesets) section above and include a patch changeset for any published package behavior change.
97
+
98
+ ### PR and issue labeling
99
+
100
+ If you are an AI coding agent or automated bot opening a PR, please add 🤖🤖🤖 to the end of the PR title. This helps maintainers triage agent-authored contributions and is a baseline expectation for this repo — PRs without the marker that turn out to be automated may be closed without review.
101
+
102
+ The same applies to issues: prefix the title with 🤖🤖🤖 if it was opened by an agent on your behalf.
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2017 Liran Tal
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,10 @@
1
+ [![view on npm](http://img.shields.io/npm/v/gulp-mraudit.svg)](https://www.npmjs.org/package/gulp-mraudit)
2
+ [![view on npm](http://img.shields.io/npm/l/gulp-mraudit.svg)](https://www.npmjs.org/package/gulp-mraudit)
3
+ [![npm module downloads](http://img.shields.io/npm/dt/gulp-mraudit.svg)](https://www.npmjs.org/package/gulp-mraudit)
4
+ <a href="https://github.com/lirantal/gulp-mraudit/actions/workflows/ci.yml"><img src="https://github.com/lirantal/gulp-mraudit/actions/workflows/ci.yml/badge.svg?branch=master" alt="build"/></a>
5
+ [![codecov](https://codecov.io/gh/lirantal/gulp-mraudit/graph/badge.svg?token=B8sBFhmIVW)](https://codecov.io/gh/lirantal/gulp-mraudit)
6
+
7
+
1
8
  Mr. Audit validates secure code guidelines and security best practices for
2
9
  JavaScript projects.
3
10
 
@@ -97,6 +104,10 @@ Option | Description |
97
104
  `setTimeout(`, `setInterval(` | Both of these functions can result in malicious JavaScript injection similar to how `eval(` is dangerous to use.
98
105
 
99
106
 
107
+ ## Contributing
108
+
109
+ Please consult [CONTRIBUTING](./CONTRIBUTING.md) for guidelines on contributing to this project.
110
+
100
111
  # Author
101
112
 
102
113
  Liran Tal <liran.tal@gmail.com>
package/gulpfile.js CHANGED
@@ -9,7 +9,7 @@ var options = {
9
9
  ' req.body.'
10
10
  ],
11
11
  onFound: function (string, file) {
12
- var error = 'Warning: Your file contains "' + string + '", it should not.';
12
+ var error = 'Warning: Your file ' + file.history + ' contains "' + string + '", it should not.';
13
13
  console.log(error);
14
14
  }
15
15
  },
@@ -21,12 +21,12 @@ var options = {
21
21
  'setInterval('
22
22
  ],
23
23
  onFound: function (string, file) {
24
- var error = 'Error: Your file contains "' + string + '", it should not.';
24
+ var error = 'Error: Your file ' + file.history + ' contains "' + string + '", it should not.';
25
25
  console.log(error);
26
26
  }
27
27
  }
28
28
  };
29
29
 
30
- gulp.task('contains', function() {
31
- gulp.src('gulpfile.js').pipe(mraudit(options));
30
+ gulp.task('audit', function() {
31
+ gulp.src('package.json').pipe(mraudit(options));
32
32
  });