@firestone-hs/reference-data
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): Angular/RxJS config reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:zone.js | AI (phantom-deps): Angular config reference pattern; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 3.0.202 | 4 / 11 | |
| 3.0.201 | 4 / 11 | |
| 3.0.200 | 4 / 11 | |
| 3.0.199 | 4 / 11 | |
| 3.0.198 | 4 / 11 | |
| 3.0.197 | 4 / 11 | |
| 3.0.196 | 4 / 11 | |
| 3.0.195 | 4 / 11 | |
| 3.0.194 | 4 / 11 | |
| 3.0.193 | 4 / 11 | |
| 3.0.192 | 4 / 11 | |
| 3.0.191 | 4 / 11 | |
| 3.0.190 | 4 / 11 | |
| 3.0.189 | 4 / 11 | |
| 3.0.188 | 4 / 11 | |
| 3.0.187 | 4 / 11 | |
| 3.0.186 | 4 / 11 | |
| 3.0.185 | 4 / 11 | |
| 3.0.184 | 4 / 11 | |
| 3.0.183 | 4 / 11 | |
| 3.0.182 | 4 / 11 | |
| 3.0.181 | 4 / 11 | |
| 3.0.180 | 4 / 11 | |
| 3.0.179 | 4 / 11 | |
| 3.0.178 | 4 / 11 | |
| 3.0.177 | 4 / 11 | |
| 3.0.176 | 4 / 11 | |
| 3.0.175 | 4 / 11 | |
| 3.0.174 | 4 / 11 | |
| 3.0.173 | 4 / 11 | |
| 3.0.172 | 4 / 11 | |
| 3.0.171 | 4 / 11 | |
| 3.0.170 | 4 / 11 | |
| 3.0.169 | 4 / 11 | |
| 3.0.168 | 4 / 11 | |
| 3.0.167 | 4 / 11 | |
| 3.0.166 | 4 / 11 | |
| 3.0.165 | 4 / 11 | |
| 3.0.164 | 4 / 11 | |
| 3.0.162 | 4 / 11 | |
| 3.0.161 | 4 / 11 | |
| 3.0.160 | 4 / 11 | |
| 3.0.159 | 4 / 11 | |
| 3.0.158 | 4 / 11 |
v3.0.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.168
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.