@types/argparse MIT 28 versions

@types/argparse

npm Repository Homepage

TypeScript definitions for argparse

28

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:http://github.com/arcticwaters	AI (email-domain): The 'email' field is actually a GitHub profile URL, not an email address. The analyzer is misidentifying a URL as an email domain — stable false positive for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published by the official DefinitelyTyped bot (types publisher) with 10604 approved packages; lack of Sigstore provenance is a stable, acceptable characteristic of this publisher.	ai	2026/04/24

Versions (showing 28 of 28)

Version	Deps	Published
2.0.17	0 / 0	2024-10-23
2.0.16	0 / 0	2024-03-20
2.0.15	0 / 0	2024-03-05
2.0.14	0 / 0	2023-11-20
2.0.13	0 / 0	2023-11-06
2.0.12	0 / 0	2023-10-17
2.0.11	0 / 0	2023-09-22
2.0.10	0 / 0	2021-07-06
2.0.9	0 / 0	2021-07-06
2.0.8	0 / 0	2021-05-17
2.0.7	0 / 0	2021-05-16
2.0.6	0 / 0	2021-05-15
2.0.5	0 / 0	2021-01-05
2.0.4	0 / 0	2020-11-16
2.0.3	0 / 0	2020-11-15
2.0.2	0 / 0	2020-10-09
2.0.1	0 / 0	2020-10-04
2.0.0	0 / 0	2020-08-27
1.0.38	0 / 0	2019-12-31
1.0.37	0 / 0	2019-12-23
1.0.36	0 / 0	2019-02-22
1.0.35	0 / 0	2018-09-29
1.0.34	0 / 0	2018-06-01
1.0.33	0 / 0	2017-09-18
1.0.32	0 / 0	2017-09-06
1.0.31	0 / 0	2017-08-21
1.0.30	0 / 0	2016-09-19
1.0.29	0 / 0	2016-07-14

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

2 findings

HIGH Unclaimed maintainer email domain: http://github.com/arcticwaters email-domain

Maintainer email 'http://github.com/arcticwaters' uses domain 'http://github.com/arcticwaters' 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.