perfect-scrollbar — Greenflagged

Minimalistic but perfect custom scrollbar plugin

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

piotrguscioramakusref10r-jackoiprzybyszrafalseifertmako3577trochonovitzjuujisaishigure92mleciejewskibwskyascensussmolenski-mikolajmdbootstrapfkappaaidzikowskigbujanski

Keywords

frontendscrollscrollbar

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/js/min/perfect-scrollbar.jquery.js	AI (source-diff): Standard minified build output from gulp+browserify+uglify pipeline; dist/js/min/ is the expected location for production bundles.	ai	2026/04/24
source-diff	obfuscated-file:dist/js/min/perfect-scrollbar.js	AI (source-diff): Standard minified build output from gulp+browserify+uglify pipeline; dist/js/min/ is the expected location for production bundles.	ai	2026/04/24
email-domain	unclaimed-email:noraesae.net	AI (email-domain): Old email domain from prior account name; author is the same person now publishing as utatti.	ai	2026/04/24
maintainer-change	maintainer-takeover	AI (maintainer-change): Same person (Hyunje Jun) renamed npm/GitHub account from noraesae to utatti; not a takeover.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): noraesae was removed because the account was renamed to utatti; same person.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): utatti is the same author (Hyunje Jun) under a renamed account.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change reflects account rename noraesae→utatti (same person); stable for this package.	ai	2026/04/24

Versions (showing 40 of 40)

Version	Deps	Published
1.5.5	0 / 6	2022-01-12
1.5.4	0 / 6	2022-01-12
1.5.3	0 / 6	2021-10-25
1.5.2	0 / 6	2021-07-19
1.5.1	0 / 6	2021-05-06
1.5.0	0 / 6	2020-01-16
1.4.0	0 / 5	2018-06-07
1.3.0	0 / 5	2017-12-01
1.2.0	0 / 5	2017-11-07
1.1.0	0 / 5	2017-10-19
1.0.3	0 / 5	2017-10-11
1.0.2	0 / 5	2017-10-10
1.0.1	0 / 5	2017-10-10
1.0.0	0 / 5	2017-10-10
0.8.1	0 / 14	2017-09-05
0.8.0	0 / 14	2017-08-29
0.7.1	0 / 14	2017-05-27
0.7.0	0 / 14	2017-05-01
0.6.16	0 / 14	2017-01-10
0.6.15	0 / 14	2016-12-07
0.6.14	0 / 14	2016-11-04
0.6.13	0 / 14	2016-10-18
0.6.12	0 / 14	2016-07-12
0.6.11	0 / 14	2016-04-22
0.6.10	0 / 14	2016-01-23
0.6.9	0 / 14	2016-01-23
0.6.8	0 / 13	2015-12-10
0.6.7	0 / 13	2015-10-03
0.6.6	0 / 13	2015-10-03
0.6.4	0 / 12	2015-07-24
0.6.3	0 / 12	2015-07-04
0.6.2	0 / 12	2015-05-12
0.6.1	0 / 11	2015-03-05
0.6.0	0 / 11	2015-03-02
0.5.9	0 / 9	2015-02-11
0.5.8	0 / 9	2014-12-02
0.5.7	0 / 9	2014-11-05
0.5.6	0 / 7	2014-10-28
0.5.5	0 / 7	2014-10-24
0.5.4	0 / 7	2014-10-21

v1.5.5

1 finding

LOW No provenance attestation provenance

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

v1.5.4

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: smolenski-mikolaj → bwsky (on 2022-01-12) provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

4 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (noraesae) were replaced by new maintainers (gbujanski, wojstan, aidzikowski, kwilk, fkappa, marlucz, mdbootstrap, smolenski-mikolaj). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: noraesae → smolenski-mikolaj (on 2021-07-19) provenance

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

HIGH Unclaimed maintainer email domain: noraesae.net email-domain

Maintainer email '[email protected]' uses domain 'noraesae.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.5.1

4 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (noraesae) were replaced by new maintainers (mdbootstrap, mattonit, smolenski-mikolaj, fkappa). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: noraesae → smolenski-mikolaj (on 2021-05-06) provenance

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

HIGH Unclaimed maintainer email domain: noraesae.net email-domain

Maintainer email '[email protected]' uses domain 'noraesae.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.5.0

4 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (noraesae) were replaced by new maintainers (utatti). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: noraesae → mattonit (on 2020-01-16) provenance

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

HIGH Unclaimed maintainer email domain: noraesae.net email-domain

Maintainer email '[email protected]' uses domain 'noraesae.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.4.0

4 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (noraesae) were replaced by new maintainers (utatti). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: noraesae → utatti (on 2018-06-07) provenance

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

HIGH Unclaimed maintainer email domain: noraesae.net email-domain

Maintainer email '[email protected]' uses domain 'noraesae.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.16

1 finding

LOW No provenance attestation provenance

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

v0.6.15

1 finding

LOW No provenance attestation provenance

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

v0.6.14

1 finding

LOW No provenance attestation provenance

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

v0.6.13

1 finding

LOW No provenance attestation provenance

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

v0.6.12

1 finding

LOW No provenance attestation provenance

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

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.10

1 finding

LOW No provenance attestation provenance

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

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

1 finding

LOW No provenance attestation provenance

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

v0.6.6

3 findings

HIGH New obfuscated file: dist/js/min/perfect-scrollbar.jquery.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.

HIGH New obfuscated file: dist/js/min/perfect-scrollbar.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.

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

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