@escapenavigator/types
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): RxJS is an implicit dependency for NestJS types; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@nestjs/common | AI (phantom-deps): NestJS common is an implicit dependency for type definitions; stable pattern. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Reflect-metadata is a known implicit runtime dependency for NestJS; stable. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.10.145 | 7 / 2 | |
| 1.10.144 | 7 / 2 | |
| 1.10.143 | 7 / 2 | |
| 1.10.142 | 7 / 2 | |
| 1.10.141 | 7 / 2 | |
| 1.10.140 | 7 / 2 | |
| 1.10.139 | 7 / 2 | |
| 1.10.138 | 7 / 2 | |
| 1.10.137 | 7 / 2 | |
| 1.10.136 | 7 / 2 | |
| 1.10.135 | 7 / 2 | |
| 1.10.134 | 7 / 2 | |
| 1.10.133 | 7 / 2 | |
| 1.10.132 | 7 / 2 | |
| 1.10.131 | 7 / 2 | |
| 1.10.130 | 7 / 2 | |
| 1.10.129 | 7 / 2 | |
| 1.10.128 | 7 / 2 | |
| 1.10.127 | 7 / 2 | |
| 1.10.126 | 7 / 2 | |
| 1.10.125 | 7 / 2 | |
| 1.10.124 | 7 / 2 | |
| 1.10.123 | 7 / 2 | |
| 1.10.100 | 5 / 3 | |
| 1.10.96 | 5 / 3 | |
| 1.10.95 | 5 / 3 | |
| 1.10.88 | 5 / 3 | |
| 1.10.87 | 5 / 3 | |
| 1.10.81 | 5 / 3 | |
| 1.10.73 | 5 / 3 | |
| 1.10.70 | 5 / 3 | |
| 1.10.62 | 5 / 3 | |
| 1.10.61 | 5 / 3 | |
| 1.10.59 | 5 / 3 | |
| 1.10.50 | 5 / 3 | |
| 1.10.49 | 5 / 3 | |
| 1.10.46 | 5 / 3 | |
| 1.10.43 | 5 / 3 | |
| 1.10.38 | 5 / 3 | |
| 1.10.37 | 5 / 3 | |
| 1.10.31 | 5 / 3 | |
| 1.10.29 | 5 / 3 | |
| 1.10.19 | 5 / 3 | |
| 1.10.17 | 5 / 3 | |
| 1.10.15 | 5 / 3 | |
| 1.10.4 | 5 / 3 | |
| 1.10.2 | 5 / 3 |
v1.10.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.