← Home

@transferwise/components

npm Repository

Neptune React components

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

Maintainers

tw-circlecinpn_ci_wiseitservicestw-circle-public

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Test asserting sanitiser blocks file:// paths, not real /etc/passwd access. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Test asserting sanitiser blocks raw-IP URLs, not an actual raw-IP request. ai
phantom-deps phantom-dep:@popperjs/core AI (phantom-deps): Used via config/react-popper indirection, common pattern. ai
maintainer-change maintainer-added AI (maintainer-change): Same CI migration as publisher-changed; not a compromise indicator. ai
provenance publisher-changed AI (provenance): CI account transition with strong track record (62 approved, 0 rejected) and unchanged provenance. ai
publish-pattern new-deps-added AI (publish-pattern): clsx and virtua are established, widely-used packages. ai
provenance no-provenance AI (provenance): Long-established org package; no provenance is a process gap, not a security signal for this publisher. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped babel runtime; loaded by convention via babel plugin, not direct import. ai
phantom-deps phantom-dep:@transferwise/neptune-tokens AI (phantom-deps): Same-org design token package; likely consumed via CSS/Less rather than direct JS import. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): core-js is a known polyfill runtime dep; not directly imported but legitimately used via babel transform. ai

Versions (showing 84 of 84)

Version Deps Published
46.159.0 17 / 55
46.158.0 17 / 55
46.157.1 17 / 55
46.157.0 17 / 55
46.156.0 17 / 55
46.155.1 17 / 55
46.155.0 17 / 55
46.154.0 17 / 55
46.153.0 17 / 55
46.152.0 17 / 55
46.151.1 17 / 55
46.151.0 17 / 55
46.150.0 17 / 55
46.149.2 17 / 55
46.149.1 17 / 55
46.149.0 17 / 55
46.148.1 17 / 55
46.148.0 17 / 55
46.147.0 17 / 55
46.146.0 17 / 55
46.145.0 17 / 55
46.144.1 17 / 55
46.144.0 17 / 56
46.143.1 17 / 56
46.143.0 17 / 56
46.142.0 17 / 56
46.141.0 17 / 56
46.140.1 17 / 56
46.140.0 17 / 56
46.139.0 17 / 56
46.138.0 17 / 56
46.137.1 17 / 56
46.137.0 17 / 52
46.136.1 17 / 52
46.136.0 17 / 52
46.135.3 17 / 52
46.135.2 17 / 52
46.135.1 19 / 52
46.135.0 19 / 52
46.134.0 19 / 52
46.133.1 19 / 52
46.133.0 19 / 52
46.132.1 19 / 52
46.132.0 19 / 52
46.131.2 19 / 52
46.131.1 19 / 52
46.131.0 19 / 52
46.130.3 18 / 52
46.130.2 18 / 52
46.130.1 18 / 52
46.130.0 18 / 52
46.129.0 18 / 52
46.128.3 18 / 52
46.128.2 18 / 52
46.128.1 18 / 52
46.128.0 18 / 52
46.127.1 18 / 52
46.126.0 18 / 52
46.125.0 18 / 52
46.124.1 19 / 52
46.124.0 19 / 51
46.123.1 19 / 51
46.123.0 19 / 51
46.122.1 19 / 51
46.122.0 19 / 51
46.121.2 19 / 51
46.121.1 19 / 51
46.120.1 19 / 51
46.120.0 19 / 51
46.119.5 19 / 50
46.119.4 19 / 50
46.119.3 19 / 50
46.119.2 19 / 50
46.119.0 19 / 50
46.118.0 19 / 50
46.117.1 19 / 50
46.117.0 19 / 50
46.116.1 19 / 49
46.116.0 19 / 49
46.115.1 19 / 49
46.115.0 18 / 50
46.114.1 18 / 50
46.29.1 23 / 62
46.29.0 24 / 59

v46.159.0

3 findings
HIGH shady-links-raw-ip: src/Markup/utils/sanitise.test.ts:262 semgrep

HTTP request to raw IP address — legitimate packages use domain names 260 | 261 | it('blocks AWS metadata endpoint', () => { > 262 | expect(sanitiseHref('https://169.254.169.254/')).toBeUndefined(); 263 | }); 264 |

HIGH etc-passwd-access: src/Markup/utils/sanitise.test.ts:338 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 336 | describe('additional blocked protocols (regression)', () => { 337 | it('blocks file: protocol', () => { > 338 | expect(sanitiseHref('file:///etc/passwd')).toBeUndefined(); 339 | }); 340 |

INFO No provenance attestation provenance

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

v46.158.0

3 findings
HIGH shady-links-raw-ip: src/Markup/utils/sanitise.test.ts:262 semgrep

HTTP request to raw IP address — legitimate packages use domain names 260 | 261 | it('blocks AWS metadata endpoint', () => { > 262 | expect(sanitiseHref('https://169.254.169.254/')).toBeUndefined(); 263 | }); 264 |

HIGH etc-passwd-access: src/Markup/utils/sanitise.test.ts:338 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 336 | describe('additional blocked protocols (regression)', () => { 337 | it('blocks file: protocol', () => { > 338 | expect(sanitiseHref('file:///etc/passwd')).toBeUndefined(); 339 | }); 340 |

INFO No provenance attestation provenance

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

v46.157.1

3 findings
HIGH shady-links-raw-ip: src/Markup/utils/sanitise.test.ts:262 semgrep

HTTP request to raw IP address — legitimate packages use domain names 260 | 261 | it('blocks AWS metadata endpoint', () => { > 262 | expect(sanitiseHref('https://169.254.169.254/')).toBeUndefined(); 263 | }); 264 |

HIGH etc-passwd-access: src/Markup/utils/sanitise.test.ts:338 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 336 | describe('additional blocked protocols (regression)', () => { 337 | it('blocks file: protocol', () => { > 338 | expect(sanitiseHref('file:///etc/passwd')).toBeUndefined(); 339 | }); 340 |

INFO No provenance attestation provenance

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

v46.157.0

3 findings
HIGH shady-links-raw-ip: src/Markup/utils/sanitise.test.ts:262 semgrep

HTTP request to raw IP address — legitimate packages use domain names 260 | 261 | it('blocks AWS metadata endpoint', () => { > 262 | expect(sanitiseHref('https://169.254.169.254/')).toBeUndefined(); 263 | }); 264 |

HIGH etc-passwd-access: src/Markup/utils/sanitise.test.ts:338 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 336 | describe('additional blocked protocols (regression)', () => { 337 | it('blocks file: protocol', () => { > 338 | expect(sanitiseHref('file:///etc/passwd')).toBeUndefined(); 339 | }); 340 |

INFO No provenance attestation provenance

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

v46.156.0

3 findings
HIGH shady-links-raw-ip: src/Markup/utils/sanitise.test.ts:262 semgrep

HTTP request to raw IP address — legitimate packages use domain names 260 | 261 | it('blocks AWS metadata endpoint', () => { > 262 | expect(sanitiseHref('https://169.254.169.254/')).toBeUndefined(); 263 | }); 264 |

HIGH etc-passwd-access: src/Markup/utils/sanitise.test.ts:338 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 336 | describe('additional blocked protocols (regression)', () => { 337 | it('blocks file: protocol', () => { > 338 | expect(sanitiseHref('file:///etc/passwd')).toBeUndefined(); 339 | }); 340 |

INFO No provenance attestation provenance

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

v46.155.1

1 finding
INFO No provenance attestation provenance

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

v46.155.0

1 finding
INFO No provenance attestation provenance

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

v46.154.0

1 finding
INFO No provenance attestation provenance

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

v46.153.0

1 finding
INFO No provenance attestation provenance

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

v46.152.0

1 finding
INFO No provenance attestation provenance

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

v46.151.1

1 finding
INFO No provenance attestation provenance

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

v46.133.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-27) provenance

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

INFO No provenance attestation provenance

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

v46.133.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-25) provenance

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

INFO No provenance attestation provenance

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

v46.132.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-17) provenance

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

INFO No provenance attestation provenance

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

v46.132.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-13) provenance

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

INFO No provenance attestation provenance

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

v46.131.2

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-11) provenance

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

INFO No provenance attestation provenance

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

v46.131.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-09) provenance

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

INFO No provenance attestation provenance

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

v46.131.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-06) provenance

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

INFO No provenance attestation provenance

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

v46.130.3

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-05) provenance

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

INFO No provenance attestation provenance

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

v46.130.2

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-04) provenance

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

INFO No provenance attestation provenance

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

v46.130.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-04) provenance

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

INFO No provenance attestation provenance

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

v46.130.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-03-03) provenance

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

INFO No provenance attestation provenance

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

v46.129.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-20) provenance

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

INFO No provenance attestation provenance

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

v46.128.3

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-19) provenance

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

INFO No provenance attestation provenance

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

v46.128.2

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-17) provenance

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

INFO No provenance attestation provenance

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

v46.128.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-17) provenance

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

INFO No provenance attestation provenance

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

v46.128.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-16) provenance

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

INFO No provenance attestation provenance

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

v46.127.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-13) provenance

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

INFO No provenance attestation provenance

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

v46.126.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-11) provenance

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

INFO No provenance attestation provenance

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

v46.125.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-02-05) provenance

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

INFO No provenance attestation provenance

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

v46.124.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-29) provenance

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

INFO No provenance attestation provenance

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

v46.124.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-28) provenance

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

INFO No provenance attestation provenance

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

v46.123.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-28) provenance

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

INFO No provenance attestation provenance

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

v46.123.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-27) provenance

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

INFO No provenance attestation provenance

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

v46.122.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-23) provenance

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

INFO No provenance attestation provenance

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

v46.122.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-21) provenance

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

INFO No provenance attestation provenance

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

v46.121.2

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-20) provenance

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

INFO No provenance attestation provenance

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

v46.121.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-16) provenance

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

INFO No provenance attestation provenance

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

v46.120.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-13) provenance

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

INFO No provenance attestation provenance

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

v46.120.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-12) provenance

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

INFO No provenance attestation provenance

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

v46.119.5

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-09) provenance

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

INFO No provenance attestation provenance

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

v46.119.4

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-08) provenance

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

INFO No provenance attestation provenance

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

v46.119.3

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-06) provenance

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

INFO No provenance attestation provenance

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

v46.119.2

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-06) provenance

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

INFO No provenance attestation provenance

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

v46.119.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2026-01-05) provenance

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

INFO No provenance attestation provenance

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

v46.118.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-12-22) provenance

This version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.117.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-12-22) provenance

This version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.117.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-12-22) provenance

This version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.116.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-12-11) provenance

This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.116.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-12-08) provenance

This version was published by a different npm account than previous versions on 2025-12-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.115.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-11-14) provenance

This version was published by a different npm account than previous versions on 2025-11-14. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.115.0

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-11-06) provenance

This version was published by a different npm account than previous versions on 2025-11-06. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.114.1

2 findings
HIGH Publisher changed: tw-circleci → npn_ci_wise (on 2025-10-31) provenance

This version was published by a different npm account than previous versions on 2025-10-31. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v46.29.1

1 finding
INFO No provenance attestation provenance

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

v46.29.0

1 finding
INFO No provenance attestation provenance

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