← Home

coveo.analytics

npm Repository Homepage

📈 Coveo analytics client (node and browser compatible)

51
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

oa-npmcoveo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff bulk-obfuscated-files:dist AI (source-diff): Standard rollup bundled output, not true obfuscation. ai
source-diff obfuscated-file:dist/coveoua.browser.js AI (source-diff): Standard minified rollup browser bundle matching package.json's browser field. ai
provenance publisher-changed-stale AI (provenance): 1816-day stale publish, inconsistent with takeover per analyzer's own note. ai
publish-pattern new-deps-added AI (publish-pattern): cross-fetch/async-storage are well-known, function-appropriate deps. ai
maintainer-change maintainer-added AI (maintainer-change): Confirmed known-maintainer manual publish per provenance INFO finding. ai
maintainer-change maintainer-removed AI (maintainer-change): Same org transitioning npm account, not a takeover. ai
source-diff obfuscated-file:dist/library.es.js AI (source-diff): Standard minified rollup build output, not true obfuscation; matches package's stated function. ai

Versions (showing 51 of 136)

View all versions
Version Deps Published
2.30.56 4 / 35
2.30.55 4 / 35
2.30.54 4 / 35
2.30.52 4 / 35
2.30.51 4 / 35
2.30.50 4 / 35
2.30.49 4 / 35
2.30.48 4 / 35
2.30.47 4 / 35
2.30.46 4 / 35
2.30.45 4 / 35
2.30.44 4 / 35
2.30.43 4 / 35
2.30.42 4 / 35
2.30.41 4 / 35
2.30.40 4 / 35
2.30.39 4 / 35
2.30.38 4 / 35
2.30.37 4 / 35
2.30.36 4 / 35
2.30.28 4 / 35
2.30.27 4 / 35
2.30.26 4 / 35
2.30.25 4 / 35
2.30.24 4 / 35
2.30.23 5 / 34
2.30.22 5 / 34
2.30.19 5 / 34
2.30.16 5 / 34
2.30.15 5 / 34
2.30.14 5 / 34
2.30.13 5 / 34
2.30.12 5 / 34
2.30.11 5 / 31
2.30.10 5 / 31
2.30.8 5 / 31
2.30.7 5 / 31
2.30.6 5 / 31
2.30.5 5 / 31
2.30.4 5 / 31
2.30.3 5 / 31
2.28.17 4 / 31
2.23.10 1 / 30
2.23.9 1 / 30
2.23.8 1 / 30
2.23.7 1 / 30
2.23.6 1 / 30
2.23.5 1 / 30
2.23.4 1 / 30
2.23.3 1 / 30
2.23.2 1 / 30

v2.30.54

1 finding
LOW No provenance attestation provenance

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

v2.30.52

1 finding
LOW No provenance attestation provenance

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

v2.30.51

2 findings
MEDIUM Publisher changed: npmcoveo → GitHub Actions (on 2025-12-10, unremoved on npm for 221d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (npmcoveo) on 2025-12-10. It has since remained available on npm for 221 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.30.44

1 finding
LOW No provenance attestation provenance

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

v2.30.43

1 finding
LOW No provenance attestation provenance

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

v2.30.42

1 finding
LOW No provenance attestation provenance

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

v2.30.41

1 finding
LOW No provenance attestation provenance

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

v2.30.40

1 finding
LOW No provenance attestation provenance

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

v2.30.39

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: pixhel → npmcoveo (on 2024-10-01, known maintainer) provenance

This version was published by a different npm account (npmcoveo) than the most recent previously approved version (pixhel) on 2024-10-01, but npmcoveo 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.

v2.30.38

1 finding
LOW No provenance attestation provenance

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

v2.30.37

1 finding
LOW No provenance attestation provenance

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

v2.30.36

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: nlegros → pixhel (on 2024-09-09, known maintainer) provenance

This version was published by a different npm account (pixhel) than the most recent previously approved version (nlegros) on 2024-09-09, but pixhel 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.

v2.30.28

1 finding
LOW No provenance attestation provenance

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

v2.30.27

1 finding
LOW No provenance attestation provenance

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

v2.30.26

1 finding
LOW No provenance attestation provenance

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

v2.30.25

1 finding
LOW No provenance attestation provenance

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

v2.30.24

1 finding
LOW No provenance attestation provenance

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

v2.30.23

1 finding
LOW No provenance attestation provenance

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

v2.30.22

1 finding
LOW No provenance attestation provenance

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

v2.30.19

1 finding
LOW No provenance attestation provenance

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

v2.30.16

1 finding
LOW No provenance attestation provenance

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

v2.30.15

1 finding
LOW No provenance attestation provenance

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

v2.30.14

1 finding
LOW No provenance attestation provenance

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

v2.30.13

1 finding
LOW No provenance attestation provenance

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

v2.30.12

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: ndlr → nlegros (on 2024-07-19, known maintainer) provenance

This version was published by a different npm account (nlegros) than the most recent previously approved version (ndlr) on 2024-07-19, but nlegros 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.

v2.30.11

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: ndlr → nlegros (on 2024-07-17, known maintainer) provenance

This version was published by a different npm account (nlegros) than the most recent previously approved version (ndlr) on 2024-07-17, but nlegros 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.

v2.30.10

1 finding
LOW No provenance attestation provenance

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

v2.30.8

1 finding
LOW No provenance attestation provenance

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

v2.30.7

1 finding
LOW No provenance attestation provenance

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

v2.30.6

1 finding
LOW No provenance attestation provenance

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

v2.30.5

1 finding
LOW No provenance attestation provenance

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

v2.30.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.

v2.30.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.

v2.28.17

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: flguillemette → ndlr (on 2023-09-14, unremoved on npm for 1040d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (flguillemette) on 2023-09-14. It has since remained available on npm for 1040 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.10

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2023-01-16, unremoved on npm for 1281d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2023-01-16. It has since remained available on npm for 1281 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.9

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2023-01-10, unremoved on npm for 1287d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2023-01-10. It has since remained available on npm for 1287 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.8

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-12-14, unremoved on npm for 1313d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-12-14. It has since remained available on npm for 1313 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.7

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-12-13, unremoved on npm for 1315d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-12-13. It has since remained available on npm for 1315 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.6

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-12-03, unremoved on npm for 1325d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-12-03. It has since remained available on npm for 1325 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.5

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-11-28, unremoved on npm for 1330d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-11-28. It has since remained available on npm for 1330 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.4

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-11-18, unremoved on npm for 1339d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-11-18. It has since remained available on npm for 1339 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.3

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-11-16, unremoved on npm for 1341d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-11-16. It has since remained available on npm for 1341 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.23.2

3 findings
HIGH New obfuscated file: dist/coveoua.browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

MEDIUM Publisher changed: coveo-organization → ndlr (on 2022-11-07, unremoved on npm for 1350d) provenance

This version was published by a different npm account (ndlr) than the most recent previously approved version (coveo-organization) on 2022-11-07. It has since remained available on npm for 1350 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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