@compilr-dev/cli
AI-powered coding assistant CLI using @compilr-dev/agents
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@compilr-dev/ui-core | AI (dependencies): First-party @compilr-dev scoped package; consistent with the rest of the org's dependency graph. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added deps (cli-highlight, cli-table3, highlight.js) are established, benign display/formatting libraries. | ai | |
| license | uncommon-license:FSL-1.1-MIT | AI (license): FSL-1.1-MIT is a known functional source license; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): No other risk signals; absence of provenance alone is insufficient to block this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @compilr-dev/cli is a distinct AI CLI product, not a typosquat of joi. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): MCP SDK referenced in config files; consistent with AI agent CLI use case. | ai | |
| phantom-deps | phantom-dep:@anthropic-ai/sdk | AI (phantom-deps): Likely used via config/transitive path in an AI CLI; stable false positive for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.7.4 | 20 / 9 | |
| 0.7.3 | 20 / 9 | |
| 0.7.2 | 20 / 9 | |
| 0.7.1 | 20 / 9 | |
| 0.7.0 | 18 / 9 | |
| 0.6.6 | 16 / 10 | |
| 0.6.5 | 16 / 10 | |
| 0.6.4 | 16 / 10 | |
| 0.6.3 | 16 / 10 | |
| 0.6.2 | 16 / 10 | |
| 0.6.1 | 16 / 10 | |
| 0.6.0 | 16 / 10 | |
| 0.5.17 | 16 / 10 | |
| 0.5.16 | 15 / 10 | |
| 0.5.15 | 15 / 10 | |
| 0.5.14 | 15 / 10 | |
| 0.5.13 | 15 / 10 | |
| 0.5.12 | 15 / 10 | |
| 0.5.11 | 15 / 10 | |
| 0.5.10 | 15 / 10 | |
| 0.5.9 | 15 / 10 | |
| 0.5.8 | 15 / 10 | |
| 0.5.7 | 15 / 10 | |
| 0.5.6 | 15 / 10 | |
| 0.5.5 | 15 / 10 | |
| 0.5.4 | 15 / 10 | |
| 0.5.3 | 15 / 10 | |
| 0.5.2 | 15 / 10 | |
| 0.5.1 | 14 / 10 | |
| 0.5.0 | 11 / 7 | |
| 0.4.0 | 8 / 7 |
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.