@plasmicpkgs/plasmic-pigeon-maps
Plasmic Pigeon maps components.
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:dlv | AI (phantom-deps): dlv is a direct runtime dependency; phantom-dep heuristic misfires on this package. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): change-case is a direct runtime dependency; phantom-dep heuristic misfires on this package. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.0.87 | 3 / 9 | |
| 0.0.86 | 3 / 9 | |
| 0.0.85 | 3 / 9 | |
| 0.0.84 | 3 / 9 | |
| 0.0.83 | 3 / 9 | |
| 0.0.82 | 3 / 9 | |
| 0.0.81 | 3 / 9 | |
| 0.0.80 | 3 / 9 | |
| 0.0.79 | 3 / 9 | |
| 0.0.78 | 3 / 9 | |
| 0.0.77 | 3 / 9 | |
| 0.0.76 | 3 / 9 | |
| 0.0.75 | 3 / 9 | |
| 0.0.74 | 3 / 9 | |
| 0.0.73 | 3 / 9 | |
| 0.0.72 | 3 / 9 | |
| 0.0.71 | 3 / 9 | |
| 0.0.70 | 3 / 9 | |
| 0.0.69 | 3 / 9 | |
| 0.0.68 | 3 / 9 | |
| 0.0.67 | 3 / 9 | |
| 0.0.66 | 3 / 9 | |
| 0.0.65 | 3 / 9 | |
| 0.0.64 | 3 / 9 | |
| 0.0.63 | 3 / 9 | |
| 0.0.62 | 3 / 9 | |
| 0.0.61 | 3 / 9 | |
| 0.0.60 | 3 / 9 | |
| 0.0.59 | 3 / 9 | |
| 0.0.58 | 3 / 9 | |
| 0.0.57 | 3 / 11 | |
| 0.0.56 | 3 / 11 | |
| 0.0.55 | 3 / 11 | |
| 0.0.54 | 3 / 11 | |
| 0.0.53 | 3 / 11 | |
| 0.0.52 | 3 / 11 | |
| 0.0.51 | 3 / 11 | |
| 0.0.50 | 3 / 11 | |
| 0.0.49 | 3 / 11 | |
| 0.0.48 | 3 / 11 | |
| 0.0.47 | 3 / 11 | |
| 0.0.46 | 3 / 11 | |
| 0.0.45 | 3 / 11 | |
| 0.0.44 | 3 / 11 | |
| 0.0.43 | 3 / 11 | |
| 0.0.42 | 3 / 11 | |
| 0.0.41 | 3 / 11 | |
| 0.0.40 | 3 / 11 | |
| 0.0.39 | 3 / 11 | |
| 0.0.38 | 3 / 11 | |
| 0.0.37 | 3 / 11 |
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.