not able to run ampstart project on my local dev

after getting a clone from https://github.com/ampproject/ampstart

I have started following README.md

after running command 'npm i'

i got following error
```

vr@vr ~/git/ampstart2 $ npm i

> kickstart@ postinstall /home/vr/git/ampstart2
> cd functions && npm i

npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
audited 153 packages in 2.178s
found 23 vulnerabilities (7 low, 12 moderate, 4 high)
run `npm audit fix` to fix them, or `npm audit` for details
audited 16373 packages in 14.26s
found 3 vulnerabilities (2 low, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
```
then I tried 'npm audit' and i got following audit results
```
vr@vr ~/git/ampstart2 $ npm audit

=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance

Critical Command Injection
Package open
Patched in No patch available
Dependency of gulp-webserver [dev]
Path gulp-webserver > open
More info https://nodesecurity.io/advisories/663

Low Prototype Pollution
Package lodash
Patched in >=4.17.5
Dependency of highlights [dev]
Path highlights > first-mate-select-grammar > lodash
More info https://nodesecurity.io/advisories/577

Low Regular Expression Denial of Service
Package debug
Patched in >= 2.6.9 < 3.0.0 || >= 3.1.0
Dependency of gulp-webserver [dev]
Path gulp-webserver > tiny-lr > debug
More info https://nodesecurity.io/advisories/534

found 3 vulnerabilities (2 low, 1 critical) in 16373 scanned packages
3 vulnerabilities require manual review. See the full report for details.
```
I tried 'npm audit fix' and 'npm audit fix --force' still it do nothing
```
vr@vr ~/git/ampstart2 $ npm audit fix
up to date in 10.408s
fixed 0 of 3 vulnerabilities in 16373 scanned packages
3 vulnerabilities required manual review and could not be updated
vr@vr ~/git/ampstart2 $ npm audit fix --force
npm WARN using --force I sure hope you know what you are doing.
up to date in 10.884s
fixed 0 of 3 vulnerabilities in 16373 scanned packages
3 vulnerabilities required manual review and could not be updated
```
even then after i tried 'npm run build' and got following error, I am unable to build and run this project,
```
> kickstart@ build /home/vr/git/ampstart2
> gulp build

/home/vr/git/ampstart2/node_modules/gulp-help/index.js:81
task = gulp.tasks[name];
^

TypeError: Cannot read property 'help' of undefined
at Gulp.gulp.task (/home/vr/git/ampstart2/node_modules/gulp-help/index.js:81:22)
at module.exports (/home/vr/git/ampstart2/node_modules/gulp-help/index.js:97:8)
at Object. (/home/vr/git/ampstart2/gulpfile.js:17:34)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:20:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kickstart@ build: `gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the kickstart@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vr/.npm/_logs/2018-08-18T08_44_54_307Z-debug.log
```
-----------------------------------------------------------------------------------------------

Please help

Vinay
vinkrins@gmail.com

I have started a group for AmpStart project, pls join to help

https://join.slack.com/t/ampstart/shared_invite/enQtNDE4NzMxNTQzMDQ0LWI5ZmYxZGIwMzUxZDdkNjcyMDY4ZGIxNmFhNzQxZWU0YjE0ZGE3Y2I4MGM5MzU2MDE4MjIyYWU2N2QzZjQ5ODM

Start with README.md and gulpfile.js, then reproduce the failure with npm i and npm run build. Check how gulp-help is invoked at gulpfile.js:17 and whether the reported npm audit warnings are separate from the build error. Done means the documented local setup completes and npm run build succeeds.

Written by the indexing model from the issue text.