@globalart/nestjs-typeorm-outbox
TypeORM Outbox integration for NestJS
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cron | AI (phantom-deps): NestJS library peer/transitive dep pattern; declared for type resolution, not directly imported. | ai | |
| phantom-deps | phantom-dep:kafkajs | AI (phantom-deps): Microservices transport dep; declared for optional transport support, not directly imported. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): Standard NestJS peer dep pattern; stable false positive for NestJS integration libraries. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Bundled ESM/CJS output; lodash may be inlined or tree-shaken, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@globalart/text-utils | AI (phantom-deps): Same-org dependency; likely used indirectly via bundled output rather than direct import. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 4 / 5 | |
| 4.0.2 | 4 / 5 | |
| 4.0.1 | 4 / 5 | |
| 1.8.0 | 4 / 6 | |
| 1.7.4 | 6 / 6 | |
| 1.7.3 | 6 / 6 | |
| 1.7.2 | 5 / 6 | |
| 1.7.1 | 5 / 6 | |
| 1.7.0 | 5 / 6 | |
| 1.6.1 | 5 / 6 | |
| 1.6.0 | 5 / 6 | |
| 1.5.0 | 5 / 6 | |
| 1.4.0 | 6 / 6 | |
| 1.3.3 | 10 / 6 | |
| 1.3.2 | 10 / 6 | |
| 1.3.1 | 10 / 6 | |
| 1.3.0 | 10 / 6 | |
| 1.2.2 | 10 / 6 | |
| 1.2.1 | 10 / 6 | |
| 1.1.1 | 10 / 6 | |
| 1.1.0 | 10 / 6 | |
| 1.0.16 | 10 / 6 | |
| 1.0.15 | 10 / 6 | |
| 1.0.14 | 10 / 6 | |
| 1.0.13 | 10 / 6 | |
| 1.0.12 | 10 / 6 | |
| 1.0.11 | 10 / 6 | |
| 1.0.10 | 10 / 6 | |
| 1.0.9 | 10 / 6 | |
| 1.0.8 | 10 / 6 | |
| 1.0.7 | 10 / 6 | |
| 1.0.6 | 11 / 6 | |
| 1.0.5 | 11 / 6 | |
| 1.0.4 | 11 / 6 | |
| 1.0.3 | 11 / 6 | |
| 1.0.2 | 11 / 6 | |
| 1.0.1 | 11 / 6 | |
| 1.0.0 | 11 / 6 |
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.