amphtml-validator

Official validator for AMP HTML (www.ampproject.org)

amphtml-validator@1.0.38 was published on 2024-04-02. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All amphtml-validator versions · Permanent reference to 1.0.38

Package specifications

Version1.0.38
License declarationApache-2.0
Published2024-04-02T01:58:05.838Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size30.75 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars14904
Repository forks4052

Install amphtml-validator 1.0.38

npm install amphtml-validator@1.0.38
pnpm add amphtml-validator@1.0.38
yarn add amphtml-validator@1.0.38

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
SAST9/10 — SAST tool detected but not run on all commits
Fuzzing10/10 — project is fuzzed

Evidence and freshness