← Home

@donmahallem/turbo-pb

npm Repository Homepage

Protobuf Helpers for express.js

43
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

donmahallem

Keywords

expresshelpers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@donmahallem/turbo AI (dependencies): Same-author monorepo sibling dependency; expected and stable across versions. ai

Versions (showing 43 of 43)

Version Deps Published
3.2.62 1 / 6
3.2.61 1 / 6
3.2.60 1 / 6
3.2.59 1 / 6
3.2.58 1 / 6
3.2.57 1 / 6
3.2.56 1 / 6
3.2.55 1 / 6
3.2.54 1 / 6
3.2.53 1 / 6
3.2.52 1 / 6
3.2.51 1 / 6
3.2.50 1 / 6
3.2.49 1 / 6
3.2.48 1 / 6
3.2.47 1 / 6
3.2.46 1 / 6
3.2.45 1 / 6
3.2.43 1 / 6
3.2.42 1 / 6
3.2.41 1 / 6
3.2.40 1 / 6
3.2.39 1 / 6
3.2.38 1 / 6
3.2.36 1 / 6
3.2.35 1 / 6
3.2.34 1 / 6
3.2.33 1 / 6
3.2.32 1 / 6
3.2.31 1 / 6
3.2.30 1 / 6
3.2.28 1 / 6
3.2.27 1 / 6
3.2.26 1 / 6
3.2.25 1 / 6
3.2.24 1 / 6
3.2.23 1 / 6
3.2.1 1 / 6
3.2.0 1 / 6
3.1.1 1 / 6
3.1.0 1 / 6
3.0.1 1 / 6
3.0.0 1 / 6

v3.2.62

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.

v3.2.61

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.

v3.2.60

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.

v3.2.59

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.

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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