@m5kdev/backend
Composable Express server stack with Drizzle ORM and tRPC.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency CI-driven publishing pattern consistent across 77 versions in 86 days. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth tracks new modules (pdf, docx, notification, video, etc.) added in this release. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Package is a growing backend framework; new feature-aligned deps are expected on each release. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Rapid module expansion is consistent with this package's development pattern (71 versions in 76 days). | ai | |
| dependencies | unvetted-dep:ffmpeg-ffprobe-static | AI (dependencies): ffmpeg-ffprobe-static is a well-known static binary package; use in a video module is expected. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package with consistent publishing history; lack of Sigstore attestation is acceptable here. | ai | |
| phantom-deps | phantom-dep:trpc-to-openapi | AI (phantom-deps): tRPC OpenAPI module in exports; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-sts | AI (phantom-deps): AWS SDK STS loaded transitively via S3 presigner; stable false positive. | ai | |
| phantom-deps | phantom-dep:@libsql/client | AI (phantom-deps): LibSQL client loaded via Drizzle ORM config convention. | ai | |
| phantom-deps | phantom-dep:rrule | AI (phantom-deps): Recurrence module present in exports; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:ioredis | AI (phantom-deps): Redis-backed queue (bullmq) pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React peer dep for SSR/email rendering; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@posthog/ai | AI (phantom-deps): PostHog AI module present in exports; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/multer | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Likely re-exported or used via config convention in a framework package. | ai | |
| phantom-deps | phantom-dep:@m5kdev/config | AI (phantom-deps): Same-org sibling package; likely loaded by convention. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Dev/logging dep loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Common config-time dep, referenced in config files as noted. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.20.34 | 54 / 19 | |
| 0.20.32 | 54 / 19 | |
| 0.19.3 | 53 / 19 | |
| 0.17.7 | 53 / 19 | |
| 0.17.5 | 53 / 19 | |
| 0.17.0 | 53 / 19 | |
| 0.16.6 | 53 / 19 | |
| 0.16.3 | 53 / 19 | |
| 0.15.2 | 53 / 19 | |
| 0.14.0 | 53 / 19 | |
| 0.9.1 | 49 / 19 | |
| 0.8.8 | 47 / 18 | |
| 0.8.7 | 47 / 18 | |
| 0.8.3 | 48 / 19 | |
| 0.7.0 | 48 / 18 |
v0.20.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: reion.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.