← Home

@loafmarkets/shared-types

npm

Shared contracts for Loaf Markets frontend, backend, and matching engine.

100
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zzzzzzzzw1gavinloafcrinas21anaickergourabloaf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): anaicker is an established publisher (54 approved, 0 rejected) within the @loafmarkets org; transition appears legitimate. ai
phantom-deps phantom-dep:@loafmarkets/shared-types AI (phantom-deps): Self-referential same-org phantom dep is a known artifact of this package's build/publish pattern; not a security risk. ai
dependencies unvetted-dep:@loafmarkets/shared-types AI (dependencies): Package lists itself as a dependency (same org scope); quirky but not malicious. Consistent across versions. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); no other risk signals elevate this concern for this package. ai

Versions (showing 100 of 151)

Version Deps Published
1.0.177 2 / 3
1.0.176 2 / 3
1.0.175 2 / 3
1.0.174 2 / 3
1.0.173 2 / 3
1.0.172 2 / 3
1.0.171 2 / 3
1.0.170 2 / 3
1.0.169 2 / 3
1.0.168 2 / 3
1.0.167 2 / 3
1.0.166 2 / 3
1.0.165 2 / 3
1.0.164 2 / 3
1.0.163 2 / 3
1.0.162 2 / 3
1.0.161 2 / 3
1.0.160 2 / 3
1.0.159 2 / 3
1.0.158 2 / 3
1.0.157 2 / 3
1.0.156 2 / 3
1.0.155 2 / 3
1.0.154 2 / 3
1.0.153 2 / 3
1.0.151 2 / 3
1.0.150 2 / 3
1.0.149 2 / 3
1.0.148 2 / 3
1.0.147 2 / 3
1.0.146 2 / 3
1.0.144 2 / 3
1.0.143 2 / 3
1.0.142 2 / 3
1.0.141 2 / 3
1.0.140 2 / 3
1.0.139 2 / 3
1.0.138 2 / 3
1.0.137 2 / 3
1.0.136 2 / 3
1.0.135 2 / 3
1.0.134 2 / 3
1.0.132 2 / 3
1.0.131 2 / 3
1.0.130 2 / 3
1.0.129 2 / 3
1.0.128 2 / 3
1.0.127 2 / 3
1.0.126 2 / 3
1.0.125 2 / 3
1.0.124 2 / 3
1.0.123 2 / 3
1.0.122 2 / 3
1.0.121 2 / 3
1.0.120 2 / 3
1.0.119 2 / 3
1.0.118 2 / 3
1.0.110 2 / 3
1.0.107 2 / 3
1.0.105 2 / 3
1.0.104 2 / 3
1.0.103 2 / 3
1.0.102 2 / 3
1.0.101 2 / 3
1.0.100 2 / 3
1.0.99 2 / 3
1.0.98 2 / 3
1.0.97 2 / 3
1.0.96 2 / 3
1.0.95 2 / 3
1.0.94 2 / 3
1.0.93 2 / 3
1.0.92 2 / 3
1.0.91 2 / 3
1.0.90 2 / 3
1.0.89 2 / 3
1.0.88 2 / 3
1.0.87 2 / 3
1.0.86 2 / 3
1.0.85 2 / 3
1.0.84 2 / 3
1.0.83 2 / 3
1.0.82 2 / 3
1.0.81 2 / 3
1.0.80 2 / 3
1.0.79 2 / 3
1.0.78 2 / 3
1.0.74 2 / 3
1.0.73 2 / 3
1.0.72 2 / 3
1.0.71 2 / 3
1.0.70 2 / 3
1.0.69 2 / 3
1.0.68 2 / 3
1.0.67 2 / 3
1.0.66 2 / 3
1.0.65 2 / 3
1.0.64 2 / 3
1.0.63 2 / 3
1.0.62 2 / 3
Showing 100 of 151 Next page →

v1.0.177

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: crinas21 → gourabloaf (on 2026-07-21, known maintainer) provenance

This version was published by a different npm account (gourabloaf) than the most recent previously approved version (crinas21) on 2026-07-21, but gourabloaf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.176

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1 finding
INFO No provenance attestation provenance

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