@comet/cms-api BSD-2-Clause 44 versions

@comet/cms-api

npm Repository Homepage

Comet CMS API package

44

Versions

BSD-2-Clause

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

kaufmofranzeldkarnutschnsamsmanuelblumvividplanetjohnnyomair

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:passport	AI (phantom-deps): Framework-level dep loaded via NestJS convention, not direct import.	ai	2026/05/22
phantom-deps	phantom-dep:@nestjs/jwt	AI (phantom-deps): NestJS module loaded by convention, not direct import.	ai	2026/05/22
phantom-deps	phantom-dep:@smithy/node-http-handler	AI (phantom-deps): AWS SDK transitive dep pinned for known issue; loaded by convention.	ai	2026/05/22
semgrep	semgrep:base64-decode	AI (semgrep): Standard Basic Auth header parsing; not hiding payloads.	ai	2026/05/17
semgrep	semgrep:hex-decode	AI (semgrep): HMAC key/salt hex decoding for imgproxy URL signing; legitimate crypto use.	ai	2026/05/17
semgrep	semgrep:dynamic-require	AI (semgrep): Loads migration files from a known directory; controlled input, not arbitrary user data.	ai	2026/05/17

Versions (showing 44 of 44)

Version	Deps	Published
8.24.0	38 / 46	2026-06-03
8.23.4	38 / 46	2026-05-27
8.23.3	38 / 46	2026-05-26
8.23.2	38 / 46	2026-05-18
8.23.1	38 / 46	2026-05-11
8.23.0	38 / 46	2026-05-07
8.22.0	38 / 46	2026-05-05
8.21.1	38 / 46	2026-04-28
8.21.0	38 / 46	2026-04-20
8.20.4	38 / 46	2026-04-08
8.20.3	38 / 46	2026-04-08
8.20.2	38 / 46	2026-03-24
8.20.1	38 / 46	2026-03-23
8.20.0	38 / 46	2026-03-17
8.19.0	38 / 46	2026-03-10
8.18.0	38 / 46	2026-03-05
8.17.1	38 / 46	2026-02-23
8.17.0	38 / 46	2026-02-23
8.16.0	38 / 46	2026-02-19
8.15.0	38 / 46	2026-02-18
8.14.0	38 / 46	2026-02-03
8.13.0	38 / 46	2026-01-29
8.12.0	37 / 45	2026-01-22
8.11.1	37 / 45	2026-01-15
8.11.0	37 / 45	2026-01-12
8.10.0	37 / 45	2025-12-09
8.9.0	37 / 44	2025-12-02
8.8.0	37 / 44	2025-11-28
8.7.1	37 / 44	2025-11-20
8.7.0	37 / 44	2025-11-19
8.6.0	38 / 44	2025-11-11
8.5.2	38 / 44	2025-11-03
8.5.1	38 / 44	2025-10-28
8.5.0	39 / 44	2025-10-15
8.4.2	39 / 44	2025-10-13
8.4.0	39 / 44	2025-10-10
8.3.0	39 / 44	2025-09-29
8.2.0	39 / 44	2025-09-05
8.1.1	39 / 44	2025-09-01
8.1.0	39 / 44	2025-08-28
8.0.0	39 / 44	2025-08-07
7.25.14	50 / 44	2025-11-13
7.25.13	50 / 44	2025-11-03
7.25.12	50 / 44	2025-11-03

v8.24.0

1 finding

LOW No provenance attestation provenance

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

v8.23.4

1 finding

LOW No provenance attestation provenance

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

v8.23.3

1 finding

LOW No provenance attestation provenance

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

v8.23.2

1 finding

LOW No provenance attestation provenance

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

v8.23.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.

v8.23.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.

v8.22.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.

v8.21.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.

v8.21.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.

v8.20.4

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.

v8.20.3

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.

v8.20.2

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.

v8.20.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.

v8.20.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.

v8.19.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.

v8.18.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.

v8.17.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.

v8.17.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.

v8.16.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.

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

v8.14.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.

v8.13.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.

v8.12.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.

v8.11.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.

v8.11.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.

v8.10.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.

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

v8.8.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.

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

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

v8.6.0

1 finding

LOW No provenance attestation provenance

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

v8.5.2

1 finding

LOW No provenance attestation provenance

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

v8.5.1

1 finding

LOW No provenance attestation provenance

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

v8.5.0

1 finding

LOW No provenance attestation provenance

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

v8.4.2

1 finding

LOW No provenance attestation provenance

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

v8.4.0

1 finding

LOW No provenance attestation provenance

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

v8.3.0

1 finding

LOW No provenance attestation provenance

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

v8.2.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.

v8.1.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.

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

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

v7.25.14

1 finding

LOW No provenance attestation provenance

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

v7.25.13

1 finding

LOW No provenance attestation provenance

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

v7.25.12

1 finding

LOW No provenance attestation provenance

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