@linker-design-plus/tiny-peony
a simple editor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in dependencies, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Declared in dependencies, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Declared in dependencies, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@zcsol/shared | AI (phantom-deps): Declared in dependencies, referenced in config; heuristic false positive for this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 1.4.43 | 8 / 9 | |
| 1.4.42 | 8 / 9 | |
| 1.4.40 | 8 / 9 | |
| 1.4.39 | 8 / 9 | |
| 1.4.38 | 8 / 9 | |
| 1.4.37 | 8 / 9 | |
| 1.4.36 | 8 / 9 | |
| 1.4.25 | 7 / 9 | |
| 1.4.22 | 6 / 9 | |
| 1.4.21 | 6 / 9 | |
| 1.4.20 | 6 / 9 | |
| 1.4.19 | 6 / 9 | |
| 1.4.18 | 6 / 9 | |
| 1.4.17 | 6 / 9 | |
| 1.4.16 | 6 / 9 | |
| 1.4.15 | 6 / 9 | |
| 1.4.13 | 6 / 9 | |
| 1.4.12 | 6 / 9 | |
| 1.4.11 | 6 / 9 | |
| 1.4.10 | 6 / 9 | |
| 1.4.9 | 6 / 9 | |
| 1.4.8 | 6 / 9 | |
| 1.4.7 | 6 / 9 | |
| 1.4.6 | 6 / 9 | |
| 1.4.5 | 6 / 9 | |
| 1.4.4 | 6 / 9 | |
| 1.4.3 | 6 / 9 | |
| 1.4.2 | 6 / 9 | |
| 1.4.1 | 6 / 9 | |
| 1.4.0 | 6 / 9 | |
| 1.3.12 | 6 / 9 | |
| 1.3.11 | 6 / 9 | |
| 1.3.10 | 6 / 9 | |
| 1.3.9 | 6 / 9 | |
| 1.3.8 | 6 / 9 | |
| 1.3.7 | 6 / 9 | |
| 1.3.6 | 6 / 9 | |
| 1.3.5 | 6 / 9 | |
| 1.3.4 | 6 / 9 | |
| 1.3.3 | 6 / 9 | |
| 1.3.2 | 6 / 9 | |
| 1.3.1 | 6 / 9 | |
| 1.3.0 | 6 / 9 | |
| 1.2.41 | 6 / 9 | |
| 1.2.40 | 6 / 9 | |
| 1.2.39 | 6 / 9 | |
| 1.2.38 | 6 / 9 | |
| 1.2.37 | 6 / 9 | |
| 1.2.36 | 6 / 9 | |
| 1.2.35 | 6 / 9 | |
| 1.2.34 | 6 / 9 |
v1.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.