@milaboratories/pf-plots
Utility library for data choosing interface inputs in graph-maker
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
Versions (showing 100 of 120)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 3 / 8 | |
| 1.4.6 | 3 / 8 | |
| 1.4.5 | 3 / 8 | |
| 1.4.4 | 3 / 8 | |
| 1.4.3 | 3 / 8 | |
| 1.4.2 | 3 / 8 | |
| 1.4.1 | 3 / 8 | |
| 1.4.0 | 3 / 8 | |
| 1.3.0 | 3 / 8 | |
| 1.2.1 | 2 / 8 | |
| 1.2.0 | 2 / 8 | |
| 1.1.70 | 2 / 8 | |
| 1.1.69 | 2 / 8 | |
| 1.1.68 | 2 / 8 | |
| 1.1.61 | 2 / 8 | |
| 1.1.60 | 2 / 8 | |
| 1.1.59 | 2 / 8 | |
| 1.1.58 | 2 / 8 | |
| 1.1.57 | 2 / 8 | |
| 1.1.56 | 2 / 8 | |
| 1.1.55 | 4 / 8 | |
| 1.1.54 | 4 / 8 | |
| 1.1.53 | 4 / 8 | |
| 1.1.52 | 4 / 8 | |
| 1.1.51 | 4 / 8 | |
| 1.1.50 | 4 / 8 | |
| 1.1.49 | 4 / 8 | |
| 1.1.48 | 4 / 8 | |
| 1.1.47 | 4 / 8 | |
| 1.1.46 | 4 / 8 | |
| 1.1.45 | 4 / 12 | |
| 1.1.44 | 4 / 20 | |
| 1.1.43 | 4 / 19 | |
| 1.1.28 | 4 / 17 | |
| 1.1.27 | 4 / 15 | |
| 1.1.26 | 4 / 15 | |
| 1.1.25 | 4 / 15 | |
| 1.1.24 | 4 / 15 | |
| 1.1.23 | 3 / 15 | |
| 1.1.22 | 3 / 15 | |
| 1.1.21 | 3 / 15 | |
| 1.1.20 | 3 / 15 | |
| 1.1.19 | 3 / 15 | |
| 1.1.18 | 3 / 15 | |
| 1.1.17 | 3 / 15 | |
| 1.1.16 | 3 / 15 | |
| 1.1.15 | 3 / 15 | |
| 1.1.14 | 3 / 15 | |
| 1.1.13 | 3 / 15 | |
| 1.1.12 | 3 / 15 | |
| 1.1.11 | 3 / 15 | |
| 1.1.10 | 3 / 15 | |
| 1.1.9 | 3 / 15 | |
| 1.1.8 | 3 / 15 | |
| 1.1.7 | 3 / 15 | |
| 1.1.6 | 3 / 15 | |
| 1.1.5 | 3 / 15 | |
| 1.1.4 | 3 / 15 | |
| 1.1.3 | 3 / 15 | |
| 1.1.2 | 3 / 15 | |
| 1.1.1 | 3 / 15 | |
| 1.1.0 | 3 / 15 | |
| 1.0.99 | 3 / 15 | |
| 1.0.98 | 3 / 15 | |
| 1.0.97 | 3 / 15 | |
| 1.0.96 | 3 / 15 | |
| 1.0.95 | 3 / 15 | |
| 1.0.94 | 3 / 16 | |
| 1.0.93 | 3 / 16 | |
| 1.0.92 | 3 / 16 | |
| 1.0.91 | 3 / 16 | |
| 1.0.90 | 3 / 16 | |
| 1.0.89 | 3 / 16 | |
| 1.0.88 | 3 / 16 | |
| 1.0.87 | 3 / 16 | |
| 1.0.86 | 3 / 16 | |
| 1.0.85 | 3 / 16 | |
| 1.0.84 | 3 / 16 | |
| 1.0.83 | 3 / 16 | |
| 1.0.82 | 3 / 16 | |
| 1.0.81 | 3 / 16 | |
| 1.0.80 | 3 / 16 | |
| 1.0.79 | 3 / 16 | |
| 1.0.78 | 3 / 16 | |
| 1.0.77 | 3 / 16 | |
| 1.0.76 | 3 / 16 | |
| 1.0.75 | 3 / 15 | |
| 1.0.74 | 3 / 15 | |
| 1.0.73 | 3 / 15 | |
| 1.0.72 | 3 / 15 | |
| 1.0.71 | 3 / 15 | |
| 1.0.70 | 3 / 15 | |
| 1.0.69 | 3 / 15 | |
| 1.0.68 | 3 / 15 | |
| 1.0.67 | 3 / 15 | |
| 1.0.66 | 3 / 15 | |
| 1.0.65 | 3 / 15 | |
| 1.0.64 | 3 / 15 | |
| 1.0.63 | 3 / 15 | |
| 1.0.62 | 3 / 15 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.