← Home

smoothscroll-polyfill

npm Repository Homepage

Smooth Scroll behavior polyfill

15
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

iamdustanjeremenichellijiyinyiyong

Keywords

smoothscrollCSSOMpolyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established package with long-standing maintainer; missing gitHead is a cosmetic publish-environment difference, not a code integrity signal for this package. ai
source-diff source-size-dropped AI (source-diff): Package ships built dist artifacts; source size drop is a diff-tool artifact from comparing untracked src/ directories, not a real code replacement. ai
provenance publisher-changed AI (provenance): iamdustan is the original package author (repo owner); jeremenichelli was a contributor who had publishing rights. The change back to the original author is legitimate and consistent with package.json authorship. ai
publish-pattern dormant-publish AI (publish-pattern): smoothscroll-polyfill is a stable browser API polyfill; long dormancy between releases is expected and not indicative of account takeover. ai

Versions (showing 15 of 15)

Version Deps Published
0.4.4 0 / 8
0.4.3 0 / 8
0.4.2 0 / 8
0.4.1 0 / 8
0.4.0 0 / 3
0.3.6 0 / 4
0.3.5 0 / 4
0.3.4 0 / 4
0.3.3 0 / 4
0.3.2 0 / 6
0.3.1 0 / 6
0.3.0 0 / 6
0.2.1 0 / 4
0.2.0 0 / 4
0.1.0 0 / 4

v0.4.4

2 findings
HIGH Publisher changed: jeremenichelli → iamdustan (on 2019-03-26) provenance

This version was published by a different npm account than previous versions on 2019-03-26. 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.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jeremenichelli.

LOW No provenance attestation provenance

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

v0.4.1

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jeremenichelli.

v0.4.0

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: iamdustan → jeremenichelli (on 2017-09-22) provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

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: jeremenichelli → iamdustan (on 2017-04-21) provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

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: jiyinyiyong → jeremenichelli (on 2016-05-31) provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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