@tobilu/qmd
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tree-sitter-typescript | AI (phantom-deps): Same as tree-sitter-go — dynamically loaded grammar, referenced in config files. | ai | |
| phantom-deps | phantom-dep:tree-sitter-go | AI (phantom-deps): Tree-sitter grammars are loaded dynamically via config; not directly imported in JS but legitimately used. | ai | |
| phantom-deps | phantom-dep:tree-sitter-rust | AI (phantom-deps): Same as tree-sitter-go — dynamically loaded grammar, referenced in config files. | ai | |
| phantom-deps | phantom-dep:tree-sitter-python | AI (phantom-deps): Same as tree-sitter-go — dynamically loaded grammar, referenced in config files. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA provenance attestation; CI/CD publishing is the documented release flow. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread is in a test runner script that passes env to child processes — standard pattern, not exfiltration. | ai | |
| source-diff | obfuscated-file:dist/embedded-skills.js | AI (source-diff): File contains base64-encoded embedded skill markdown data, not obfuscated malicious code; pattern is stable for this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): zod is a declared dependency of this package; clearly not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @tobilu/qmd; name similarity to qs is coincidental, not impersonation. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.5.3 | 13 / 3 | |
| 2.5.2 | 13 / 3 | |
| 2.5.1 | 13 / 3 | |
| 2.1.0 | 9 / 3 | |
| 2.0.1 | 8 / 3 | |
| 2.0.0 | 8 / 3 | |
| 1.1.6 | 8 / 3 | |
| 1.1.5 | 8 / 3 | |
| 1.1.2 | 8 / 3 | |
| 1.1.1 | 8 / 3 | |
| 1.0.7 | 8 / 3 | |
| 1.0.6 | 8 / 3 | |
| 1.0.5 | 8 / 3 | |
| 1.0.0 | 8 / 3 | |
| 0.9.0 | 5 / 1 |
v2.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.1
3 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/tobi/qmd/blob/ba6538090fbd929e835c1aafaa75ab1ede60682c/scripts/test-all.mjs#L15 13 | stdio: "inherit", 14 | shell: process.platform === "win32", > 15 | env: { ...process.env, ...(extraEnv ?? {}) }, 16 | ...spawnOptions, 17 | });
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.