@dewtech/dare-cli MIT 27 versions

@dewtech/dare-cli

npm Repository Homepage

DARE Framework - CLI, GraphRAG engine, MCP server and shared types in a single package

27

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

wleandro.oliveira

Keywords

darecliai-assisteddevelopmentmcpknowledge-graphgraphragmodel-context-protocol

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@dewtech/dare-core	AI (phantom-deps): Same-org monorepo sibling; CLI may use it indirectly via dynamic imports or re-exports.	ai	2026/05/11
phantom-deps	phantom-dep:@dewtech/dare-graphrag	AI (phantom-deps): Same-org monorepo sibling; consistent with CLI orchestrating sibling packages.	ai	2026/05/11
phantom-deps	phantom-dep:@dewtech/dare-mcp-server	AI (phantom-deps): Same-org monorepo sibling; consistent with CLI orchestrating sibling packages.	ai	2026/05/11

Versions (showing 27 of 27)

Version	Deps	Published
2.17.0	12 / 16	2026-05-15
2.16.0	12 / 16	2026-05-14
2.15.0	12 / 16	2026-05-08
2.14.0	12 / 16	2026-05-08
2.13.0	12 / 16	2026-05-08
2.12.0	12 / 16	2026-05-08
2.11.0	12 / 16	2026-05-08
2.10.0	12 / 16	2026-05-08
2.9.0	12 / 16	2026-05-07
2.7.0	12 / 16	2026-05-06
2.6.0	12 / 16	2026-05-05
2.5.0	12 / 16	2026-05-05
2.4.1	12 / 16	2026-05-05
2.4.0	12 / 16	2026-05-05
2.3.1	12 / 16	2026-05-05
2.3.0	12 / 16	2026-05-05
2.2.0	15 / 16	2026-05-05
2.1.0	12 / 16	2026-05-05
2.0.1	12 / 16	2026-05-05
2.0.0	12 / 16	2026-05-05
0.3.5	9 / 10	2026-05-04
0.3.3	9 / 10	2026-05-04
0.3.2	9 / 10	2026-05-04
0.3.1	9 / 10	2026-05-04
0.3.0	9 / 10	2026-05-04
0.2.0	9 / 10	2026-05-02
0.1.0	6 / 10	2026-05-02

v2.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wleandro.oliveira.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wleandro.oliveira.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.