@spinajs/orm-threading MIT 8 versions

@spinajs/orm-threading

npm Repository Homepage

utility functions shared across @spinajs framework

8

Versions

MIT

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

gben-spina

Keywords

spinajshttp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@spinajs/di	AI (phantom-deps): Same-org monorepo dep; declared but used transitively, stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@spinajs/exceptions	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@spinajs/log-common	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/29

Versions (showing 8 of 108)

Version	Deps	Published
2.0.370	6 / 0	2025-06-04
2.0.369	6 / 0	2025-05-27
2.0.368	6 / 0	2025-05-23
2.0.367	6 / 0	2025-05-22
2.0.363	6 / 0	2025-05-16
2.0.362	6 / 0	2025-05-16
2.0.361	6 / 0	2025-05-12
2.0.360	6 / 0	2025-05-07

v2.0.370

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.

v2.0.369

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.

v2.0.368

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.

v2.0.367

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.

v2.0.363

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.

v2.0.362

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.

v2.0.361

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.

v2.0.360

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.