npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cogita/plugin-content-check

v0.2.5

Published

Cogita 内容质量与构建诊断插件。

Readme

@cogita/plugin-content-check

Cogita 的内容质量与构建诊断插件,用于在静态构建阶段发现文章或普通文档的元数据、路由和本地图片引用问题。

export default defineConfig({
  contentCheck: {
    enabled: true,
    reportPath: 'content-report.json',
    failOnError: false,
    requiredFields: ['title', 'date'],
    checkImages: true,
    checkImageAlt: true,
    checkRoutes: true,
    checkEmptyContent: true,
    checkLinks: true,
    severity: {
      'missing-link': 'warning',
    },
    ignores: [{ code: 'missing-link', route: '/posts/legacy' }],
  },
});

插件默认只输出警告和 JSON 报告,不会改变现有构建结果。可以用 severity 按问题代码调整为 error、warning 或 ignore,也可以用 ignores 按代码、路由或文件路径忽略特定问题。需要将内容错误纳入 CI 门禁时,再显式设置 failOnError: true。报告会在构建继续失败时尽可能提前写入,便于 CI 保留诊断结果。

报告使用统一的 schemaVersion: 1、reportType: "content-check"、itemCount、errors、warnings 和 issues 字段。构建后可以使用仓库中的 scripts/check-quality-reports.mjs 合并内容与 SEO 报告,并通过 --max-errors、--max-warnings 设置 CI 门禁;GitHub Actions 会自动生成 annotation。插件通过统一 ContentIndex 同时检查文章和普通文档,普通文档可以不提供 date frontmatter。