Gathering detailed insights and metrics for @ampproject/toolbox-validator-rules
Gathering detailed insights and metrics for @ampproject/toolbox-validator-rules
Gathering detailed insights and metrics for @ampproject/toolbox-validator-rules
Gathering detailed insights and metrics for @ampproject/toolbox-validator-rules
@types/amphtml-validator
TypeScript definitions for amphtml-validator
@ampproject/toolbox-optimizer
Server-side rendering for AMPs.
@ampproject/toolbox-script-csp
A library that calculates the CSP hash for amp-script
@ampproject/remapping
Remap sequential sourcemaps through transformations to point at the original source code
A collection of AMP tools making it easier to publish and host AMP pages.
npm install @ampproject/toolbox-validator-rules
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
450 Stars
1,312 Commits
243 Forks
43 Watching
61 Branches
110 Contributors
Updated on 15 Nov 2024
HTML (78.83%)
JavaScript (15.43%)
TypeScript (3.36%)
CSS (2.36%)
Handlebars (0.01%)
Dockerfile (0.01%)
Cumulative downloads
Total Downloads
Last day
22.9%
9,353
Compared to previous day
Last week
19%
54,249
Compared to previous week
Last month
15%
185,180
Compared to previous month
Last year
-45.3%
2,195,083
Compared to previous year
1
A collection of AMP tools making it easier to publish and host AMP pages. The following tools are part of this project:
amp-script
compatible CSP hashes.After forking amp-toolbox to your own github org, do the following steps to get started:
# clone your fork to your local machine
git clone https://github.com/your-fork/amp-toolbox.git
# step into local repo
cd amp-toolbox
# install dependencies
npm install
# run tests
npm test
amp-toolbox uses Lerna to manage it's packages. To keep build times low, devDependencies
(but not CLI dependencies) must be added to the root package.json file. Runtime dependencies are managed for each package individually.
When adding a new package inside the packages
directory, register the package via:
npm run bootstrap
The test suite runs for all packages and must be run from the root directory.
# run tests on node and browser
npm test
# run only in node (fastest)
npm run test:node
# run only in browser
npm run test:browser
Using additional arguments the node tests can generate a coverage report or run only for a specific package.
# generate a coverage report
npm run test:node -- --collectCoverage
# run only tests for AMP Optimizer
npm run test:node -- packages/optimizer
This codebase adheres to the Google Javascript Styleguide and is enforced using ESLint. ESLint is run as part of the test suite, but you can also explicity run it via:
# run ESLint
npm run lint
# run ESLint with `--fix` option to automatically fix errors (if possible)
npm run lint:fix
Before publishing a release, make sure to have the lates changes from master and the changelog is up-to-date:
$ npm run changelog
This will print all changes since the previous release. For this to work, all PRs need to be correctly labeled as:
breaking
(💥 Breaking Change)enhancement
(🚀 Enhancement)bug
(🐛 Bug Fix)documentation
(📝 Documentation)internal
(🏠 Internal)Copy and prepend the new changes to CHANGELOG.md when you're about to make a release. Don't forget to update the version. Commit the updated changelog and run:
$ npm publish
to publish all changed packages to NPM. Pick the new version according to SemVer.
Please see the CONTRIBUTING file for information on contributing to the AMP Project.
AMP Toolbox is made by the AMP Project, and is licensed under the Apache License, Version 2.0.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 13/19 approved changesets -- score normalized to 6
Reason
0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
87 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More