@spinajs/orm-mysql
orm mysql integration
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:asn1 | AI (phantom-deps): Transitive dep via ssh2; declared in package.json for clarity. | ai | |
| phantom-deps | phantom-dep:bcrypt-pbkdf | AI (phantom-deps): Transitive dep via ssh2; declared in package.json for clarity. | ai | |
| phantom-deps | phantom-dep:@spinajs/configuration | AI (phantom-deps): Same-org monorepo dep; stable pattern for this package. | ai |
Versions (showing 19 of 419)
| Version | Deps | Published |
|---|---|---|
| 2.0.56 | 5 / 2 | |
| 2.0.55 | 5 / 2 | |
| 2.0.54 | 5 / 2 | |
| 2.0.53 | 5 / 2 | |
| 2.0.52 | 5 / 2 | |
| 2.0.51 | 5 / 2 | |
| 2.0.46 | 5 / 2 | |
| 2.0.45 | 5 / 2 | |
| 2.0.44 | 5 / 2 | |
| 2.0.38 | 5 / 2 | |
| 2.0.28 | 5 / 2 | |
| 2.0.26 | 5 / 2 | |
| 2.0.21 | 5 / 2 | |
| 2.0.20 | 5 / 2 | |
| 2.0.19 | 5 / 2 | |
| 2.0.17 | 5 / 3 | |
| 2.0.16 | 5 / 3 | |
| 2.0.14 | 5 / 3 | |
| 2.0.12 | 5 / 3 |
v2.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.