@types/hammerjs MIT 25 versions

@types/hammerjs

npm Repository Homepage

TypeScript definitions for hammerjs

25

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.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:https://github.com/milkisevil/	AI (email-domain): The 'email' field is actually a GitHub profile URL used in the author string, not a real email address. No actual email domain is at risk of hijacking. This is a stable false positive for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): DefinitelyTyped @types packages published by the trusted 'types' publisher do not use Sigstore provenance; this is expected and stable across all versions.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
2.0.46	0 / 0	2024-10-07
2.0.45	0 / 0	2023-11-21
2.0.44	0 / 0	2023-11-07
2.0.43	0 / 0	2023-10-18
2.0.42	0 / 0	2023-09-16
2.0.41	0 / 0	2021-12-23
2.0.40	0 / 0	2021-07-06
2.0.39	0 / 0	2021-02-19
2.0.38	0 / 0	2021-01-28
2.0.37	0 / 0	2021-01-25
2.0.36	0 / 0	2018-09-10
2.0.35	0 / 0	2017-08-21
2.0.34	0 / 0	2016-12-24
2.0.33	0 / 0	2016-09-19
2.0.32	0 / 0	2016-08-25
2.0.31	0 / 0	2016-08-19
2.0.29	0 / 0	2016-07-19
2.0.28	0 / 0	2016-07-14
1.1.6	1 / 0	2023-11-07
1.1.5	1 / 0	2023-10-18
1.1.4	1 / 0	2023-09-16
1.1.3	1 / 0	2021-07-06
1.1.2	1 / 0	2017-06-15
1.1.1	1 / 0	2017-02-28
1.1.0	1 / 0	2017-01-10

v2.0.46

1 finding

LOW No provenance attestation provenance

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

v2.0.45

1 finding

LOW No provenance attestation provenance

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

v2.0.44

1 finding

LOW No provenance attestation provenance

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

v2.0.43

1 finding

LOW No provenance attestation provenance

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

v2.0.42

1 finding

LOW No provenance attestation provenance

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

v2.0.41

1 finding

LOW No provenance attestation provenance

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

v2.0.40

1 finding

LOW No provenance attestation provenance

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

v2.0.39

1 finding

LOW No provenance attestation provenance

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

v2.0.38

1 finding

LOW No provenance attestation provenance

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

v2.0.37

1 finding

LOW No provenance attestation provenance

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

v2.0.36

1 finding

LOW No provenance attestation provenance

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

v2.0.35

1 finding

LOW No provenance attestation provenance

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

v2.0.34

1 finding

LOW No provenance attestation provenance

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

v2.0.33

1 finding

LOW No provenance attestation provenance

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

v2.0.32

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.29

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/milkisevil/ email-domain

Maintainer email 'https://github.com/milkisevil/' uses domain 'https://github.com/milkisevil/' 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.28

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/milkisevil/ email-domain

Maintainer email 'https://github.com/milkisevil/' uses domain 'https://github.com/milkisevil/' 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.6

1 finding

INFO No provenance attestation provenance

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

v1.1.5

1 finding

INFO No provenance attestation provenance

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

v1.1.4

1 finding

INFO No provenance attestation provenance

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

v1.1.3

1 finding

INFO No provenance attestation provenance

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

v1.1.2

1 finding

INFO No provenance attestation provenance

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

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

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