vue-meta 1.1.0
manage page meta info in Vue 2.0 server-rendered apps
vue-meta@1.1.0 was published on 2017-08-15. 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.
Deprecated: vue-meta is no longer maintained. See https://github.com/nuxt/vue-meta/issues/808
All vue-meta versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-08-15T09:01:57.325Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/vue-meta.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 4066 |
| Repository forks | 237 |
Install vue-meta 1.1.0
npm install vue-meta@1.1.0 pnpm add vue-meta@1.1.0 yarn add vue-meta@1.1.0
Runtime dependencies
- deepmerge ^1.5.0
- object-assign ^4.1.1
- lodash.isplainobject ^4.0.6
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.
- deepmerge@1.5.2 — direct
- lodash.isplainobject@4.0.6 — direct
- object-assign@4.1.1 — direct
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.
| Code-Review | 3/10 — Found 9/30 approved changesets -- score normalized to 3 |
|---|---|
| Maintained | 0/10 — project is archived |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 9/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 10/10 — security policy file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/vue-meta/1.1.0 — retrieved 2026-10-29T10:20:51.968Z
- https://api.deps.dev/v3/projects/github.com%2Fnuxt%2Fvue-meta — retrieved 2026-10-29T07:19:31.493Z
- https://api.deps.dev/v3/systems/npm/packages/vue-meta/versions/1.1.0 — retrieved 2026-10-29T10:20:52.532Z
- https://api.deps.dev/v3/systems/npm/packages/vue-meta/versions/1.1.0:dependencies — retrieved 2026-10-29T10:20:52.555Z