@spinajs/orm-http MIT 22 versions

@spinajs/orm-http

npm Repository Homepage

Orm extensions for HTTP module

22

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

gben-spina

Keywords

spinajsrbac

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:luxon	AI (phantom-deps): Runtime dependency used indirectly through ORM framework; stable pattern.	ai	2026/04/30
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Runtime dependency used indirectly through ORM framework; stable pattern.	ai	2026/04/30
phantom-deps	phantom-dep:@spinajs/log	AI (phantom-deps): Same-org scoped monorepo dependency; stable pattern for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@spinajs/intl-orm	AI (phantom-deps): Same-org scoped monorepo dependency; stable pattern for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@spinajs/configuration	AI (phantom-deps): Same-org scoped monorepo dependency; stable pattern for this package.	ai	2026/04/30

Versions (showing 22 of 426)

Version	Deps	Published
2.0.57	9 / 1	2023-01-27
2.0.56	9 / 1	2023-01-27
2.0.55	9 / 1	2023-01-27
2.0.54	9 / 1	2023-01-27
2.0.53	9 / 1	2023-01-27
2.0.52	9 / 1	2023-01-27
2.0.51	9 / 1	2023-01-27
2.0.46	9 / 1	2023-01-20
2.0.45	9 / 1	2023-01-19
2.0.44	9 / 1	2023-01-18
2.0.38	10 / 1	2022-09-13
2.0.28	10 / 3	2022-07-19
2.0.26	10 / 3	2022-07-19
2.0.25	10 / 3	2022-07-19
2.0.24	10 / 3	2022-07-19
2.0.23	10 / 3	2022-07-19
2.0.21	10 / 3	2022-07-19
2.0.20	10 / 3	2022-07-19
2.0.19	10 / 3	2022-07-19
2.0.15	10 / 3	2022-07-15
2.0.14	10 / 3	2022-07-15
2.0.12	10 / 3	2022-07-14

v2.0.57

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.