← Home

typings-core

npm Repository Homepage

The logic of Typings

41
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

blakeembrey

Keywords

typingscoretypescriptdefinitiondeclarationpackagemanager

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): listify is a well-known, benign utility package. Addition is consistent with the package's purpose and publisher's track record. ai
dependencies unvetted-dep:popsicle AI (dependencies): popsicle is a legitimate HTTP client used by typings-core to fetch remote type definitions; its presence is expected and consistent across versions. ai
provenance no-provenance AI (provenance): Package is 10+ years old, predates Sigstore provenance on npm. No provenance is expected and not a risk signal for this established package. ai
dependencies unvetted-dep:make-error-cause AI (dependencies): make-error-cause is a small, well-known error utility used throughout the typings ecosystem; stable dependency for this package. ai

Versions (showing 41 of 41)

Version Deps Published
2.3.3 32 / 10
2.3.1 32 / 10
2.3.0 32 / 10
2.2.0 32 / 10
2.1.0 33 / 10
2.0.0 33 / 11
1.6.1 32 / 10
1.5.0 31 / 10
1.4.1 31 / 10
1.3.1 31 / 10
1.2.4 31 / 10
1.2.3 31 / 10
1.2.2 31 / 10
1.2.1 31 / 10
1.1.3 31 / 10
1.1.0 31 / 10
1.0.1 30 / 10
1.0.0 30 / 10
0.3.1 30 / 9
0.3.0 30 / 9
0.2.16 30 / 9
0.2.15 30 / 9
0.2.14 29 / 9
0.2.13 29 / 9
0.2.12 29 / 9
0.2.11 29 / 9
0.2.10 29 / 9
0.2.9 29 / 9
0.2.8 29 / 9
0.2.7 29 / 8
0.2.6 29 / 8
0.2.5 30 / 7
0.2.4 30 / 7
0.2.3 30 / 7
0.2.2 30 / 7
0.2.1 30 / 7
0.2.0 30 / 7
0.1.2 30 / 7
0.1.1 29 / 7
0.1.0 29 / 7
0.0.0 29 / 7

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.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.

v2.3.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.

v2.2.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.

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

v2.0.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.

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

v1.4.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.3.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.2.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.2.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.2.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.2.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.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.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.

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