@owox/backend
OWOX Data Marts Backend - Full-stack data orchestration platform
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a monorepo workspace placeholder version, not throwaway malware pattern. | ai | |
| phantom-deps | phantom-dep:mysql | AI (phantom-deps): TypeORM driver loaded dynamically at runtime, not statically imported. | ai | |
| phantom-deps | phantom-dep:@nestjs/platform-express | AI (phantom-deps): NestJS module used via DI/bootstrap, not direct import. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Monorepo backend growth, no injected/obfuscated code found. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): OTel instrumentation wired via NestJS module config, not direct import. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-base | AI (phantom-deps): OTel SDK loaded by convention for tracing setup. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): OTel SDK loaded by convention for tracing setup. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): OTel exporter wired via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@google-cloud/storage | AI (phantom-deps): Framework-scoped GCP package, loaded by convention. | ai | |
| phantom-deps | phantom-dep:@google-cloud/opentelemetry-cloud-trace-exporter | AI (phantom-deps): GCP tracing exporter wired via config. | ai | |
| phantom-deps | phantom-dep:@huggingface/transformers | AI (phantom-deps): Likely dynamically loaded ML dep; no malicious behavior found. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @modelcontextprotocol/sdk is an official, established package; addition is consistent with the platform's stated function. | ai | |
| phantom-deps | phantom-dep:class-transformer | AI (phantom-deps): NestJS serialization dep; used via decorators/config, not direct imports. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): NestJS decorator runtime dep; always implicitly used, never directly imported. | ai | |
| phantom-deps | phantom-dep:sqlite3 | AI (phantom-deps): TypeORM optional driver; registered in config, not directly imported in source. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a well-known templating library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:nestjs-cls | AI (dependencies): nestjs-cls is a popular NestJS CLS library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:swagger-ui-express | AI (phantom-deps): NestJS Swagger optional dep; referenced via config, not direct import. | ai | |
| phantom-deps | phantom-dep:mysql2 | AI (phantom-deps): TypeORM optional driver; declared for runtime use without direct import in source. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): TypeORM optional driver; declared for runtime use without direct import in source. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a peer/optional dep in NestJS ecosystem; not directly imported but legitimately declared. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.30.1 | 53 / 26 | |
| 0.30.0 | 53 / 26 | |
| 0.29.0 | 47 / 26 | |
| 0.28.0 | 46 / 26 | |
| 0.27.1 | 45 / 26 | |
| 0.27.0 | 45 / 26 | |
| 0.26.0 | 45 / 26 | |
| 0.25.0 | 45 / 26 | |
| 0.24.0 | 45 / 26 | |
| 0.23.0 | 45 / 26 | |
| 0.22.0 | 44 / 26 | |
| 0.21.1 | 44 / 25 | |
| 0.21.0 | 44 / 25 | |
| 0.20.0 | 44 / 25 | |
| 0.19.0 | 44 / 25 | |
| 0.18.0 | 44 / 24 | |
| 0.17.0 | 43 / 24 | |
| 0.16.0 | 43 / 20 | |
| 0.15.0 | 42 / 20 | |
| 0.14.0 | 40 / 20 | |
| 0.13.0 | 39 / 20 | |
| 0.12.0 | 29 / 20 | |
| 0.11.0 | 29 / 19 | |
| 0.10.0 | 28 / 19 | |
| 0.9.0 | 28 / 19 | |
| 0.8.0 | 28 / 19 | |
| 0.7.0 | 28 / 19 | |
| 0.6.0 | 27 / 19 | |
| 0.5.0 | 27 / 19 | |
| 0.4.0 | 25 / 18 | |
| 0.3.0 | 25 / 18 | |
| 0.2.0 | 25 / 18 | |
| 0.1.0 | 24 / 18 | |
| 0.0.0 | 17 / 17 |
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.