@apipass/pipes
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Declared dependency; used in Angular library bundle. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Declared dependency; implicit runtime dependency for Angular. | ai | |
| phantom-deps | phantom-dep:@ngx-translate/core | AI (phantom-deps): Declared dependency; used in bundled library code. | ai | |
| phantom-deps | phantom-dep:@ngx-translate/http-loader | AI (phantom-deps): Declared dependency; used in bundled library code. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.0.201 | 5 / 0 | |
| 1.0.200 | 5 / 0 | |
| 1.0.199 | 5 / 0 | |
| 1.0.198 | 5 / 0 | |
| 1.0.197 | 5 / 0 | |
| 1.0.196 | 5 / 0 | |
| 1.0.195 | 5 / 0 | |
| 1.0.194 | 5 / 0 | |
| 1.0.193 | 5 / 0 | |
| 1.0.192 | 5 / 0 | |
| 1.0.191 | 5 / 0 | |
| 1.0.190 | 5 / 0 | |
| 1.0.189 | 5 / 0 | |
| 1.0.188 | 5 / 0 | |
| 1.0.187 | 5 / 0 | |
| 1.0.186 | 5 / 0 | |
| 1.0.185 | 5 / 0 | |
| 1.0.184 | 5 / 0 | |
| 1.0.183 | 5 / 0 | |
| 1.0.182 | 5 / 0 | |
| 1.0.181 | 5 / 0 | |
| 1.0.180 | 5 / 0 | |
| 1.0.179 | 5 / 0 | |
| 1.0.178 | 5 / 0 | |
| 1.0.177 | 5 / 0 | |
| 1.0.176 | 5 / 0 | |
| 1.0.175 | 5 / 0 | |
| 1.0.174 | 5 / 0 | |
| 1.0.173 | 5 / 0 | |
| 1.0.172 | 5 / 0 | |
| 1.0.171 | 5 / 0 | |
| 1.0.170 | 5 / 0 | |
| 1.0.167 | 5 / 0 | |
| 1.0.161 | 5 / 0 | |
| 1.0.160 | 5 / 0 | |
| 1.0.159 | 5 / 0 | |
| 1.0.158 | 5 / 0 | |
| 1.0.157 | 5 / 0 | |
| 1.0.156 | 5 / 0 | |
| 1.0.155 | 5 / 0 | |
| 1.0.154 | 5 / 0 | |
| 1.0.153 | 5 / 0 | |
| 1.0.152 | 5 / 0 | |
| 1.0.151 | 5 / 0 | |
| 1.0.150 | 5 / 0 | |
| 1.0.149 | 5 / 0 | |
| 1.0.148 | 5 / 0 | |
| 1.0.147 | 5 / 0 | |
| 1.0.146 | 5 / 0 |
v1.0.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.