ts-interface-checker Apache-2.0 19 versions

ts-interface-checker

npm Repository Homepage

Runtime library to validate data against TypeScript interfaces

19

Versions

Apache-2.0

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

paulfitzdsagal2

Keywords

typescripttsinterfacetypevalidatevalidatorcheck

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change dsagal2→paulfitz in 2018 reflects a legitimate Grist Labs internal handoff; both parties are associated with the same org and repo. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): paulfitz is a Grist Labs maintainer; addition is consistent with the org's ownership of this package. No evidence of compromise.	ai	2026/04/24

Versions (showing 19 of 19)

Version	Deps	Published
1.0.2	0 / 13	2021-10-11
1.0.1	0 / 13	2021-10-11
1.0.0	0 / 13	2021-04-14
0.2.1	0 / 13	2021-02-26
0.2.0	0 / 13	2021-02-21
0.1.13	0 / 13	2020-08-04
0.1.12	0 / 13	2020-07-29
0.1.11	0 / 13	2020-05-17
0.1.10	0 / 13	2019-12-18
0.1.9	0 / 13	2019-08-29
0.1.8	0 / 13	2019-08-27
0.1.7	0 / 13	2019-01-16
0.1.6	0 / 13	2018-10-30
0.1.5	0 / 13	2018-10-27
0.1.4	0 / 13	2018-06-15
0.1.3	0 / 13	2018-04-13
0.1.2	0 / 13	2018-04-12
0.1.1	0 / 13	2018-01-28
0.1.0	0 / 13	2018-01-11

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

2 findings

HIGH Publisher changed: dsagal2 → paulfitz (on 2018-04-13) provenance

This version was published by a different npm account than previous versions on 2018-04-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.2

2 findings

HIGH Publisher changed: dsagal2 → paulfitz (on 2018-04-12) provenance

This version was published by a different npm account than previous versions on 2018-04-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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