convex-helpers No license 39 versions

convex-helpers

npm Repository Homepage

39

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

cowlingjordanhuntgautamg795emmaling27nipunnaritrakhianatconvexdowski-convexreece-convexerquhartsethconvexjamwtnicolappsballingt

Keywords

convexbackendmigrationsratelimitdatabasereact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): child_process usage is inside the bundled commander CLI library in bin.cjs — standard sub-command dispatch for the convex-helpers CLI tool, not malicious.	ai	2026/04/25
semgrep	semgrep:child-process-spawn	AI (semgrep): spawn() calls are in commander's sub-command dispatch logic inside bin.cjs; expected behavior for a CLI binary.	ai	2026/04/25
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): 127.0.0.1:3210 is a localhost default for the test client in testing.js — local dev/test tooling, not an exfiltration endpoint.	ai	2026/04/25

Versions (showing 39 of 39)

Version	Deps	Published
0.1.119	0 / 0	2026-06-08
0.1.118	0 / 0	2026-05-15
0.1.117	0 / 0	2026-05-13
0.1.116	0 / 0	2026-05-05
0.1.115	0 / 0	2026-04-21
0.1.113	0 / 0	2026-02-20
0.1.112	0 / 0	2026-02-12
0.1.111	0 / 0	2026-01-15
0.1.110	0 / 0	2026-01-15
0.1.109	0 / 0	2026-01-10
0.1.108	0 / 0	2025-12-15
0.1.107	0 / 0	2025-12-08
0.1.106	0 / 0	2025-11-25
0.1.105	0 / 0	2025-11-17
0.1.104	0 / 0	2025-08-15
0.1.103	0 / 0	2025-08-14
0.1.102	0 / 0	2025-08-12
0.1.101	0 / 0	2025-08-05
0.1.100	0 / 0	2025-07-25
0.1.99	0 / 2	2025-07-09
0.1.98	0 / 2	2025-07-08
0.1.97	0 / 2	2025-07-08
0.1.96	0 / 2	2025-07-02
0.1.95	0 / 2	2025-06-22
0.1.94	0 / 2	2025-06-14
0.1.93	0 / 2	2025-06-12
0.1.92	0 / 2	2025-06-06
0.1.91	0 / 2	2025-06-06
0.1.90	0 / 2	2025-06-02
0.1.89	0 / 2	2025-05-23
0.1.88	0 / 2	2025-05-23
0.1.87	0 / 2	2025-05-20
0.1.86	0 / 2	2025-05-12
0.1.85	0 / 2	2025-05-05
0.1.84	0 / 2	2025-05-05
0.1.83	0 / 2	2025-05-03
0.1.82	0 / 2	2025-05-03
0.1.81	0 / 2	2025-04-29
0.1.80	0 / 2	2025-04-28

v0.1.119

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ianatconvex → nicolapps (on 2026-06-08, known maintainer) provenance

This version was published by a different npm account (nicolapps) than the most recent previously approved version (ianatconvex) on 2026-06-08, but nicolapps 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.

v0.1.118

1 finding

LOW No provenance attestation provenance

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

v0.1.117

2 findings

HIGH Publisher changed: ianatconvex → nicolapps (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.116

1 finding

LOW No provenance attestation provenance

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

v0.1.115

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

1 finding

LOW No provenance attestation provenance

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

v0.1.112

1 finding

LOW No provenance attestation provenance

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

v0.1.111

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

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

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.103

1 finding

LOW No provenance attestation provenance

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

v0.1.102

1 finding

LOW No provenance attestation provenance

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

v0.1.101

1 finding

LOW No provenance attestation provenance

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

v0.1.100

1 finding

LOW No provenance attestation provenance

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

v0.1.99

1 finding

LOW No provenance attestation provenance

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

v0.1.98

1 finding

LOW No provenance attestation provenance

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

v0.1.97

1 finding

LOW No provenance attestation provenance

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

v0.1.96

1 finding

LOW No provenance attestation provenance

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

v0.1.95

1 finding

LOW No provenance attestation provenance

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

v0.1.94

1 finding

LOW No provenance attestation provenance

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

v0.1.93

1 finding

LOW No provenance attestation provenance

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

v0.1.92

1 finding

LOW No provenance attestation provenance

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

v0.1.91

1 finding

LOW No provenance attestation provenance

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

v0.1.90

1 finding

LOW No provenance attestation provenance

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

v0.1.89

1 finding

LOW No provenance attestation provenance

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

v0.1.88

1 finding

LOW No provenance attestation provenance

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

v0.1.87

1 finding

LOW No provenance attestation provenance

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

v0.1.86

1 finding

LOW No provenance attestation provenance

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

v0.1.85

1 finding

LOW No provenance attestation provenance

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

v0.1.84

1 finding

LOW No provenance attestation provenance

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

v0.1.83

1 finding

LOW No provenance attestation provenance

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

v0.1.82

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

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

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.