@stacksjs/database
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@stacksjs/query-builder | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:@stacksjs/storage | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:@stacksjs/strings | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:kysely-bun-worker | AI (phantom-deps): Used in config, not a direct import; benign. | ai | |
| phantom-deps | phantom-dep:@stacksjs/cli | AI (phantom-deps): Same-org monorepo sibling dep, stable pattern. | ai | |
| phantom-deps | phantom-dep:@stacksjs/path | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:@stacksjs/faker | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:@stacksjs/utils | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| phantom-deps | phantom-dep:@stacksjs/config | AI (phantom-deps): Same-org monorepo sibling dep. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Coincides with CI migration; no code changes support takeover theory. | ai | |
| phantom-deps | phantom-dep:bun-query-builder | AI (phantom-deps): Used via config reference, common false positive pattern. | ai | |
| provenance | publisher-changed | AI (provenance): CI/CD migration with SLSA attestation, consistent with org's automated release adoption. | ai |
Versions (showing 73 of 173)
| Version | Deps | Published |
|---|---|---|
| 0.70.97 | 1 / 10 | |
| 0.70.96 | 1 / 10 | |
| 0.70.95 | 1 / 10 | |
| 0.70.94 | 1 / 10 | |
| 0.70.93 | 1 / 10 | |
| 0.70.92 | 1 / 10 | |
| 0.70.91 | 1 / 10 | |
| 0.70.90 | 1 / 10 | |
| 0.70.88 | 1 / 10 | |
| 0.70.87 | 1 / 10 | |
| 0.70.86 | 1 / 10 | |
| 0.70.85 | 1 / 10 | |
| 0.70.84 | 1 / 10 | |
| 0.70.83 | 1 / 10 | |
| 0.70.82 | 1 / 10 | |
| 0.70.81 | 1 / 10 | |
| 0.70.79 | 1 / 10 | |
| 0.70.78 | 1 / 10 | |
| 0.70.77 | 1 / 10 | |
| 0.70.76 | 1 / 10 | |
| 0.70.75 | 1 / 10 | |
| 0.70.74 | 1 / 10 | |
| 0.70.73 | 1 / 10 | |
| 0.70.72 | 1 / 10 | |
| 0.70.71 | 1 / 10 | |
| 0.70.70 | 1 / 10 | |
| 0.70.69 | 1 / 10 | |
| 0.70.68 | 1 / 10 | |
| 0.70.67 | 1 / 10 | |
| 0.70.66 | 1 / 10 | |
| 0.70.65 | 1 / 10 | |
| 0.70.64 | 1 / 10 | |
| 0.70.63 | 1 / 10 | |
| 0.70.62 | 1 / 10 | |
| 0.70.61 | 1 / 10 | |
| 0.70.60 | 1 / 10 | |
| 0.70.59 | 1 / 10 | |
| 0.70.58 | 1 / 10 | |
| 0.70.57 | 1 / 10 | |
| 0.70.56 | 1 / 10 | |
| 0.70.55 | 1 / 10 | |
| 0.70.54 | 1 / 10 | |
| 0.70.53 | 1 / 10 | |
| 0.70.45 | 1 / 10 | |
| 0.70.44 | 1 / 10 | |
| 0.70.43 | 1 / 10 | |
| 0.70.42 | 1 / 10 | |
| 0.70.41 | 1 / 10 | |
| 0.70.40 | 1 / 10 | |
| 0.70.39 | 1 / 10 | |
| 0.70.38 | 1 / 10 | |
| 0.70.37 | 1 / 10 | |
| 0.70.36 | 1 / 10 | |
| 0.70.35 | 1 / 10 | |
| 0.70.34 | 1 / 10 | |
| 0.70.33 | 1 / 10 | |
| 0.70.32 | 1 / 10 | |
| 0.70.31 | 1 / 10 | |
| 0.70.10 | 0 / 14 | |
| 0.70.9 | 0 / 14 | |
| 0.70.8 | 0 / 14 | |
| 0.70.7 | 0 / 14 | |
| 0.70.6 | 0 / 14 | |
| 0.70.5 | 0 / 14 | |
| 0.70.4 | 0 / 14 | |
| 0.70.3 | 0 / 14 | |
| 0.70.2 | 0 / 14 | |
| 0.70.1 | 0 / 14 | |
| 0.70.0 | 0 / 14 | |
| 0.69.3 | 0 / 14 | |
| 0.69.2 | 0 / 14 | |
| 0.69.1 | 0 / 14 | |
| 0.67.0 | 9 / 6 |
v0.70.97
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.96
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.95
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.94
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.93
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.92
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.91
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.90
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.88
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.87
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.86
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.85
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.84
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.83
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.53
2 findingsThis version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.