← Home

@types/overlayscrollbars

npm

Stub TypeScript definitions entry for overlayscrollbars, which provides its own types definitions

11
Versions
MIT
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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Stub packages from the @types publisher are published reactively when upstream ships bundled types; long dormancy followed by a stub release is the expected lifecycle for this package. ai
publish-pattern new-deps-added AI (publish-pattern): Adding overlayscrollbars as a dependency is the canonical DefinitelyTyped stub pattern — the stub depends on the real package so types resolve correctly. Not a supply-chain risk. ai
bogus-package bogus-package AI (bogus-package): DefinitelyTyped stub packages intentionally have minimal metadata (no README code, no repo, no keywords, tiny payload). This is structural, not a spam signal. ai
phantom-deps phantom-dep:overlayscrollbars AI (phantom-deps): Stub packages never import their dependency; the dep exists solely to express the types resolution relationship. Phantom-dep finding is a stable false positive for this package. ai
source-diff source-size-dropped AI (source-diff): Source dropping to 0 bytes is expected for a stub package — there are no type definitions to ship; the real package bundles them. ai

Versions (showing 11 of 11)

Version Deps Published
2.0.0 1 / 0
1.12.5 0 / 0
1.12.4 0 / 0
1.12.3 0 / 0
1.12.2 0 / 0
1.12.1 0 / 0
1.12.0 0 / 0
1.9.0 0 / 0
1.8.0 0 / 0
1.7.0 0 / 0
1.6.0 0 / 0

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.12.5

1 finding
LOW No provenance attestation provenance

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

v1.12.4

1 finding
LOW No provenance attestation provenance

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

v1.12.3

1 finding
LOW No provenance attestation provenance

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

v1.12.2

1 finding
LOW No provenance attestation provenance

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

v1.12.1

1 finding
LOW No provenance attestation provenance

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.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.