@paperclipai/db
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account (dotta) to GitHub Actions CI/CD publishing is a supply chain improvement, backed by SLSA provenance attestation. Generalizes to future versions published via the same pipeline. | ai | |
| dependencies | unvetted-dep:embedded-postgres | AI (dependencies): embedded-postgres is a legitimate library for embedding PostgreSQL; contextually appropriate for a database package. Addition is intentional and documented in package.json. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Package is a scoped internal library (@paperclipai/db) with a clear repo URL; missing description is cosmetic and not a malware indicator for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @paperclipai/db is a database utility in the paperclipai monorepo; Levenshtein match to 'pg' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @paperclipai/db has no relation to 'qs'; Levenshtein match is a false positive driven by short package name suffix. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2026.428.0 | 4 / 5 | |
| 2026.416.0 | 4 / 5 | |
| 2026.403.0 | 4 / 5 | |
| 2026.325.0 | 4 / 5 | |
| 2026.318.0 | 4 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.7 | 3 / 4 | |
| 0.2.6 | 3 / 4 | |
| 0.2.5 | 3 / 4 | |
| 0.2.4 | 3 / 4 | |
| 0.2.3 | 3 / 4 | |
| 0.2.2 | 3 / 4 |
v2026.416.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.403.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.325.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.318.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.