@convo-lang/convo-lang-pinecone No license 26 versions

@convo-lang/convo-lang-pinecone

npm Repository Homepage

26

Versions

—

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

convo-lang

Keywords

promptprompt-engineeringLLMai-agentstool-callingopen-aiaiconvo-lang

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:zod	AI (phantom-deps): Monorepo peer/config reference pattern; not a real import gap.	ai	2026/05/13
phantom-deps	phantom-dep:rxjs	AI (phantom-deps): Monorepo peer/config reference pattern; not a real import gap.	ai	2026/05/13
phantom-deps	phantom-dep:date-fns	AI (phantom-deps): Monorepo peer/config reference pattern; not a real import gap.	ai	2026/05/13
phantom-deps	phantom-dep:@iyio/vfs	AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic is a stable false positive here.	ai	2026/05/13
phantom-deps	phantom-dep:@iyio/json5	AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic is a stable false positive here.	ai	2026/05/13

Versions (showing 26 of 26)

Version	Deps	Published
0.9.7	0 / 0	2026-05-26
0.9.6	0 / 0	2026-05-26
0.9.5	0 / 0	2026-05-04
0.9.1	0 / 0	2026-04-29
0.8.18	0 / 0	2026-02-25
0.8.16	0 / 0	2025-11-27
0.8.15	0 / 0	2025-11-26
0.8.14	0 / 0	2025-11-21
0.8.13	0 / 0	2025-11-13
0.8.0	0 / 0	2025-09-21
0.7.50	7 / 0	2025-08-25
0.7.48	7 / 0	2025-08-14
0.7.47	7 / 0	2025-08-12
0.7.46	7 / 0	2025-08-10
0.7.45	7 / 0	2025-08-09
0.7.44	7 / 0	2025-08-08
0.7.43	7 / 0	2025-08-07
0.7.42	0 / 0	2025-08-02
0.7.41	7 / 0	2025-08-01
0.7.40	7 / 0	2025-08-01
0.7.39	7 / 0	2025-08-01
0.7.38	7 / 0	2025-08-01
0.7.37	7 / 0	2025-08-01
0.7.36	7 / 0	2025-08-01
0.7.34	7 / 0	2025-07-27
0.7.33	7 / 0	2025-07-25

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.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.

v0.8.18

1 finding

LOW No provenance attestation provenance

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

v0.8.16

1 finding

LOW No provenance attestation provenance

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

v0.8.15

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.8.14

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.8.13

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.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.50

1 finding

LOW No provenance attestation provenance

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

v0.7.48

1 finding

LOW No provenance attestation provenance

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

v0.7.47

1 finding

LOW No provenance attestation provenance

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

v0.7.46

1 finding

LOW No provenance attestation provenance

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

v0.7.45

1 finding

LOW No provenance attestation provenance

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

v0.7.44

1 finding

LOW No provenance attestation provenance

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

v0.7.43

1 finding

LOW No provenance attestation provenance

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

v0.7.42

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.7.41

1 finding

LOW No provenance attestation provenance

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

v0.7.40

1 finding

LOW No provenance attestation provenance

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

v0.7.39

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.7.38

1 finding

LOW No provenance attestation provenance

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

v0.7.37

1 finding

LOW No provenance attestation provenance

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

v0.7.36

1 finding

LOW No provenance attestation provenance

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

v0.7.34

1 finding

LOW No provenance attestation provenance

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

v0.7.33

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.