← Home

types-pkg-json

npm Repository Homepage

Type checking for package.json

8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

bconnorwhite

Keywords

typetypespackagejsonfieldstypescripttsobjectfile

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions as part of adopting CI/CD publishing with SLSA provenance attestation. Repository and author fields remain consistent with original maintainer bconnorwhite. ai
publish-pattern dormant-publish AI (publish-pattern): Long dormancy is expected for a stable type-definitions package. The new major version reflects legitimate modernization (new engine targets, test infrastructure) by the original author. ai

Versions (showing 8 of 8)

Version Deps Published
2.0.0 2 / 15
1.2.1 2 / 1
1.1.2 2 / 1
1.1.1 2 / 1
1.1.0 1 / 1
1.0.2 1 / 1
1.0.1 1 / 1
1.0.0 1 / 1

v2.0.0

2 findings
HIGH Publisher changed: bconnorwhite → GitHub Actions (on 2026-03-11) provenance

This version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.