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

@accountmade/questionnaire-parser

v0.1.1

Published

Parse a SIG / CAIQ / VSA / VSAQ security questionnaire (xlsx, docx, pdf, csv) into structured JSON. Ingest + normalize + framework detection only — no answers, no auto-fill.

Readme

questionnaire-parser

Parse a security questionnaire — SIG, CAIQ, VSA, VSAQ, or a bespoke one — from .xlsx, .docx, .pdf, or .csv into structured JSON: a normalized list of questions plus the detected framework(s), with evidence and confidence.

Ingest and normalize only. This library extracts and classifies questions. It does not answer them, auto-fill responses, rank answers, or ship an answer library — by design. It's the parsing primitive, nothing more.

npm install questionnaire-parser

CLI

npx qparse ./SIG-Core-2025.xlsx --pretty
npx qparse ./caiq.xlsx --questions-only > questions.json

Library

import { parseFile } from "questionnaire-parser";

const result = await parseFile("./caiq-v4.xlsx");

result.meta.questionCount;        // 261
result.primaryFramework?.name;    // "CAIQ v4 (CSA Cloud Controls Matrix)"
result.primaryFramework?.confidence; // "high"
result.questions[0];              // { id: "IAM-14", text: "Is MFA enforced…", section: "Identity & Access Management" }

Parse an in-memory buffer (e.g. a browser upload passed to a server) instead:

import { parseBuffer } from "questionnaire-parser";
const result = await parseBuffer(buffer, "xlsx", "upload.xlsx");

Or run the pure core directly on rows/text you've already extracted:

import { extractFromRows, detectFrameworks, pickPrimary } from "questionnaire-parser";

const questions = extractFromRows(rows, "Sheet1");
const frameworks = detectFrameworks(questions, rawText, sheetNames);
const primary = pickPrimary(frameworks); // null when bespoke/ambiguous

Output shape

{
  "questions": [
    { "id": "IAM-14", "text": "Is MFA enforced for privileged access?", "section": "Identity & Access Management" }
  ],
  "frameworks": [
    {
      "framework": "caiq",
      "name": "CAIQ v4 (CSA Cloud Controls Matrix)",
      "confidence": "high",
      "evidence": ["43 control IDs match the CAIQ v4 grammar", "title/header text: \"caiq\""],
      "matchedIdCount": 43,
      "source": "CSA Cloud Controls Matrix / CAIQ v4 (cloudsecurityalliance.org)",
      "score": 133
    }
  ],
  "primaryFramework": { "framework": "caiq", "...": "..." },
  "meta": { "file": "caiq-v4.xlsx", "format": "xlsx", "questionCount": 261 }
}

How detection works

One generic scorer runs over a table of framework fingerprints (control-ID grammar, header/tab strings, approximate size). There is no per-framework code branch — adding a framework is a data entry, not a new code path. ID grammar and header text dominate; question count is only a weak tiebreaker. SOC 2 and ISO 27001 are treated as cross-maps (they often appear inside another questionnaire) and are down-weighted for primary selection.

Supported fingerprints: CAIQ (CSA CCM), SIG (Shared Assessments), SOC 2, ISO 27001, Google VSAQ, Vendor Security Alliance (VSA).

Development

npm install
npm test      # runs the core tests (node:test via tsx)
npm run build # emits dist/ (ESM + types)

License

MIT. Framework names and control-ID grammars are referenced for interoperability and belong to their respective publishers (CSA, Shared Assessments, AICPA, ISO, NIST, Google).