@types/tar
Supply chain provenance
Status for the latest visible version.
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
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/somaticit | 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. No real domain hijack risk exists. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a conventional dependency for TypeScript definition packages and is not directly imported. This pattern is standard across all DefinitelyTyped packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): This stub package's sole purpose is to redirect to tar's own bundled types; the tar dependency is intentional and benign for all versions of this stub. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Package is a deprecated stub with zero source by design; size drop to 0B is expected and stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @types stub packages are intentionally minimal with no README code, no repo link, and tiny payload — this is the standard form for DefinitelyTyped stub redirects. | ai | |
| phantom-deps | phantom-dep:tar | AI (phantom-deps): The tar dependency is the intentional stub redirect mechanism, not a phantom dependency. This pattern is stable for all @types stub packages. | ai |
Versions (showing 100 of 111)
| Version | Deps | Published |
|---|---|---|
| 7.0.87 | 1 / 0 | |
| 7.0.86 | 1 / 0 | |
| 7.0.85 | 1 / 0 | |
| 7.0.84 | 1 / 0 | |
| 7.0.83 | 1 / 0 | |
| 7.0.82 | 1 / 0 | |
| 7.0.81 | 1 / 0 | |
| 7.0.80 | 1 / 0 | |
| 7.0.79 | 1 / 0 | |
| 7.0.78 | 1 / 0 | |
| 7.0.77 | 1 / 0 | |
| 7.0.76 | 1 / 0 | |
| 7.0.75 | 1 / 0 | |
| 7.0.74 | 1 / 0 | |
| 7.0.73 | 1 / 0 | |
| 7.0.72 | 1 / 0 | |
| 7.0.71 | 1 / 0 | |
| 7.0.70 | 1 / 0 | |
| 7.0.69 | 1 / 0 | |
| 7.0.68 | 1 / 0 | |
| 7.0.67 | 1 / 0 | |
| 7.0.66 | 1 / 0 | |
| 7.0.65 | 1 / 0 | |
| 7.0.64 | 1 / 0 | |
| 7.0.63 | 1 / 0 | |
| 7.0.62 | 1 / 0 | |
| 7.0.61 | 1 / 0 | |
| 7.0.60 | 1 / 0 | |
| 7.0.59 | 1 / 0 | |
| 7.0.58 | 1 / 0 | |
| 7.0.57 | 1 / 0 | |
| 7.0.56 | 1 / 0 | |
| 7.0.55 | 1 / 0 | |
| 7.0.54 | 1 / 0 | |
| 7.0.53 | 1 / 0 | |
| 7.0.52 | 1 / 0 | |
| 7.0.51 | 1 / 0 | |
| 7.0.50 | 1 / 0 | |
| 7.0.49 | 1 / 0 | |
| 7.0.48 | 1 / 0 | |
| 7.0.47 | 1 / 0 | |
| 7.0.46 | 1 / 0 | |
| 7.0.45 | 1 / 0 | |
| 7.0.44 | 1 / 0 | |
| 7.0.43 | 1 / 0 | |
| 7.0.42 | 1 / 0 | |
| 7.0.41 | 1 / 0 | |
| 7.0.40 | 1 / 0 | |
| 7.0.39 | 1 / 0 | |
| 7.0.38 | 1 / 0 | |
| 7.0.37 | 1 / 0 | |
| 7.0.36 | 1 / 0 | |
| 7.0.35 | 1 / 0 | |
| 7.0.34 | 1 / 0 | |
| 7.0.33 | 1 / 0 | |
| 7.0.32 | 1 / 0 | |
| 7.0.31 | 1 / 0 | |
| 7.0.30 | 1 / 0 | |
| 7.0.29 | 1 / 0 | |
| 7.0.28 | 1 / 0 | |
| 7.0.27 | 1 / 0 | |
| 7.0.26 | 1 / 0 | |
| 7.0.25 | 1 / 0 | |
| 7.0.24 | 1 / 0 | |
| 7.0.23 | 1 / 0 | |
| 7.0.22 | 1 / 0 | |
| 7.0.21 | 1 / 0 | |
| 7.0.20 | 1 / 0 | |
| 7.0.19 | 1 / 0 | |
| 7.0.18 | 1 / 0 | |
| 7.0.17 | 1 / 0 | |
| 7.0.16 | 1 / 0 | |
| 7.0.15 | 1 / 0 | |
| 7.0.14 | 1 / 0 | |
| 7.0.13 | 1 / 0 | |
| 7.0.12 | 1 / 0 | |
| 7.0.11 | 1 / 0 | |
| 7.0.10 | 1 / 0 | |
| 7.0.9 | 1 / 0 | |
| 7.0.8 | 1 / 0 | |
| 7.0.7 | 1 / 0 | |
| 7.0.6 | 1 / 0 | |
| 7.0.5 | 1 / 0 | |
| 7.0.4 | 1 / 0 | |
| 7.0.3 | 1 / 0 | |
| 7.0.2 | 1 / 0 | |
| 7.0.1 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.1.13 | 2 / 0 | |
| 6.1.12 | 2 / 0 | |
| 6.1.11 | 2 / 0 | |
| 6.1.10 | 2 / 0 | |
| 6.1.9 | 2 / 0 | |
| 6.1.8 | 2 / 0 | |
| 6.1.7 | 2 / 0 | |
| 6.1.6 | 2 / 0 | |
| 6.1.5 | 2 / 0 | |
| 6.1.4 | 2 / 0 | |
| 6.1.3 | 2 / 0 | |
| 6.1.2 | 2 / 0 |
v7.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.