← Home

@buildinternet/releases-api-types

npm Repository Homepage

Wire protocol — request/response types for the Releases registry API. Shared by web, workers, and clients.

52
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

zachdunn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI is a documented automation migration; no malicious indicators present. ai
publish-pattern rapid-publish AI (publish-pattern): Automated CI pipelines routinely publish in rapid succession; consistent with the GitHub Actions publisher transition. ai

Versions (showing 52 of 52)

Version Deps Published
0.49.0 2 / 0
0.48.0 2 / 0
0.47.0 2 / 0
0.46.0 2 / 0
0.45.1 2 / 0
0.45.0 2 / 0
0.44.0 2 / 0
0.43.0 2 / 0
0.42.0 2 / 0
0.41.0 2 / 0
0.40.0 2 / 0
0.39.0 2 / 0
0.38.0 2 / 0
0.37.0 2 / 0
0.36.0 2 / 0
0.35.0 2 / 0
0.34.1 2 / 0
0.34.0 2 / 0
0.33.0 2 / 0
0.32.0 2 / 0
0.31.0 2 / 0
0.30.0 2 / 0
0.29.0 2 / 0
0.28.0 2 / 0
0.27.0 2 / 0
0.26.0 2 / 0
0.25.0 2 / 0
0.24.0 2 / 0
0.23.0 2 / 0
0.22.0 2 / 0
0.21.0 2 / 0
0.20.0 2 / 0
0.19.0 2 / 0
0.18.0 2 / 0
0.17.0 2 / 0
0.16.0 2 / 0
0.15.0 2 / 0
0.14.0 2 / 0
0.13.0 2 / 0
0.12.0 2 / 0
0.11.0 2 / 0
0.10.0 2 / 0
0.9.0 2 / 0
0.8.1 2 / 0
0.8.0 2 / 0
0.7.0 0 / 0
0.6.0 0 / 0
0.5.0 0 / 0
0.4.0 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v0.49.0

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

v0.48.0

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

v0.47.0

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

v0.46.0

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

v0.45.1

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

v0.45.0

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

v0.44.0

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

v0.43.0

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

v0.42.0

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

v0.41.0

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

v0.40.0

1 finding
LOW No provenance attestation provenance

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

v0.39.0

1 finding
LOW No provenance attestation provenance

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

v0.38.0

1 finding
LOW No provenance attestation provenance

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

v0.37.0

1 finding
LOW No provenance attestation provenance

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

v0.36.0

1 finding
LOW No provenance attestation provenance

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

v0.35.0

1 finding
LOW No provenance attestation provenance

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

v0.34.1

2 findings
HIGH Publisher changed: zachdunn → GitHub Actions (on 2026-07-01) provenance

This version was published by a different npm account than previous versions on 2026-07-01. 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.34.0

1 finding
LOW No provenance attestation provenance

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

v0.17.0

1 finding
LOW No provenance attestation provenance

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