@hivehub/rulebook
Tool-agnostic AI development framework. Standardize projects across Claude Code, Cursor, Gemini, Codex, Windsurf, Copilot with automated templates, quality gates, persistent memory, and framework detection for 28 languages, 17 frameworks, 13 MCP modules,
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Direct dependency; used by transitive packages in the ecosystem. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Direct dependency; used by inquirer and config parsing. | ai | |
| phantom-deps | phantom-dep:cli-cursor | AI (phantom-deps): Direct dependency; used by inquirer for terminal UI. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Direct dependency; used by chalk and other CLI tools. | ai | |
| phantom-deps | phantom-dep:ansi-escapes | AI (phantom-deps): Direct dependency; used by blessed and terminal utilities. | ai | |
| phantom-deps | phantom-dep:node-notifier | AI (phantom-deps): Direct dependency; used for desktop notifications. | ai | |
| phantom-deps | phantom-dep:@types/blessed | AI (phantom-deps): Framework-scoped type package; loaded by convention with blessed. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.8.1 | 17 / 16 | |
| 5.8.0 | 17 / 16 | |
| 5.7.0 | 17 / 16 | |
| 5.5.2 | 18 / 17 | |
| 5.5.1 | 18 / 17 | |
| 5.5.0 | 18 / 17 | |
| 5.4.0 | 18 / 17 | |
| 5.3.3 | 18 / 16 | |
| 5.3.2 | 18 / 16 | |
| 5.3.1 | 18 / 16 | |
| 5.3.0 | 18 / 16 | |
| 5.2.1 | 18 / 16 | |
| 3.0.0 | 17 / 15 | |
| 2.1.0 | 16 / 15 | |
| 2.0.0 | 16 / 15 | |
| 1.2.0 | 16 / 15 |
v5.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (caikpigosso) than the most recent previously approved version (andrehrf) on 2026-06-01, but caikpigosso is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (caikpigosso) than the most recent previously approved version (andrehrf) on 2026-06-01, but caikpigosso is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.