postsvg
A tiny wrapper over posthml with the same API optimized for working with SVG
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established package with trusted publisher history; missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): postsvg is a legitimate utility in the svg-mixer monorepo; sparse README and no keywords are cosmetic issues, not security signals. Stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long publish history; lack of Sigstore provenance is a process gap, not a security indicator for this well-known publisher. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.2.7 | 6 / 0 | |
| 2.2.6 | 6 / 0 | |
| 2.2.5 | 6 / 0 | |
| 2.2.4 | 6 / 0 | |
| 2.2.3 | 6 / 0 | |
| 2.2.2 | 6 / 0 | |
| 2.2.1 | 6 / 0 | |
| 2.2.0 | 6 / 0 | |
| 2.1.2 | 5 / 0 | |
| 2.1.0 | 5 / 0 | |
| 2.0.0 | 4 / 0 | |
| 0.0.3 | 2 / 3 | |
| 0.0.2 | 2 / 3 | |
| 0.0.1 | 2 / 3 |
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kisenka.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.