@principal-ai/file-city-react
React components for File City visualization
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal org package; lack of Sigstore provenance is low risk given clean findings otherwise. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): lucide-react is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 0.5.79 | 2 / 20 | |
| 0.5.78 | 2 / 20 | |
| 0.5.77 | 2 / 20 | |
| 0.5.76 | 2 / 20 | |
| 0.5.75 | 2 / 20 | |
| 0.5.74 | 2 / 20 | |
| 0.5.73 | 2 / 20 | |
| 0.5.72 | 2 / 20 | |
| 0.5.71 | 2 / 20 | |
| 0.5.70 | 2 / 20 | |
| 0.5.69 | 2 / 20 | |
| 0.5.68 | 2 / 20 | |
| 0.5.67 | 2 / 20 | |
| 0.5.66 | 2 / 20 | |
| 0.5.65 | 2 / 20 | |
| 0.5.64 | 2 / 20 | |
| 0.5.63 | 2 / 20 | |
| 0.5.62 | 2 / 20 | |
| 0.5.61 | 2 / 20 | |
| 0.5.60 | 2 / 20 | |
| 0.5.59 | 2 / 20 | |
| 0.5.58 | 2 / 20 | |
| 0.5.57 | 2 / 20 | |
| 0.5.56 | 2 / 20 | |
| 0.5.55 | 2 / 20 | |
| 0.5.54 | 2 / 20 | |
| 0.5.53 | 2 / 20 | |
| 0.5.52 | 2 / 20 | |
| 0.5.51 | 2 / 20 | |
| 0.5.50 | 2 / 20 | |
| 0.5.49 | 2 / 20 | |
| 0.5.48 | 2 / 20 | |
| 0.5.47 | 2 / 20 | |
| 0.5.46 | 2 / 20 | |
| 0.5.45 | 2 / 20 | |
| 0.5.44 | 2 / 19 | |
| 0.5.43 | 2 / 19 | |
| 0.5.42 | 2 / 19 | |
| 0.5.41 | 2 / 19 | |
| 0.5.40 | 2 / 18 | |
| 0.5.39 | 2 / 18 | |
| 0.5.38 | 2 / 18 | |
| 0.5.37 | 2 / 17 | |
| 0.5.36 | 2 / 17 | |
| 0.5.35 | 2 / 17 | |
| 0.5.34 | 2 / 17 | |
| 0.5.33 | 2 / 17 | |
| 0.5.32 | 2 / 17 | |
| 0.5.31 | 6 / 13 | |
| 0.5.29 | 6 / 13 | |
| 0.5.28 | 6 / 13 |
v0.5.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.