figma-transformer
```js import { processFile } from "figma-transformer";
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 | publisher-changed | AI (provenance): Legitimate maintainer transition to souporserious (est. account, 306 approvals). Publisher change occurred in 2021; stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): souporserious added as maintainer in 2021 transition from braposo; well-established npm account with clean record. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with maintainer transition on a mature, low-churn utility package. No suspicious code changes. | ai | |
| provenance | missing-githead | AI (provenance): Established package with clean history; missing gitHead likely reflects a local publish rather than malicious activity. No other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; absence is expected for this maintainer's workflow and not indicative of risk. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 6 | |
| 2.0.8 | 0 / 8 | |
| 2.0.7 | 0 / 8 | |
| 2.0.6 | 0 / 7 | |
| 2.0.5 | 0 / 5 | |
| 2.0.4 | 0 / 5 | |
| 2.0.3 | 0 / 5 | |
| 2.0.2 | 0 / 5 | |
| 2.0.1 | 0 / 5 | |
| 2.0.0 | 0 / 5 | |
| 1.0.0 | 0 / 6 | |
| 0.1.10 | 0 / 6 | |
| 0.1.9 | 0 / 6 | |
| 0.1.8 | 0 / 6 | |
| 0.1.7 | 0 / 6 | |
| 0.1.6 | 0 / 6 | |
| 0.1.5 | 0 / 6 | |
| 0.1.4 | 0 / 6 | |
| 0.1.3 | 0 / 6 | |
| 0.1.2 | 0 / 6 | |
| 0.1.1 | 1 / 5 | |
| 0.1.0 | 3 / 6 |
v2.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: souporserious.
This version was published by a different npm account than previous versions on 2021-07-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
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: braposo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: braposo.
v2.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: braposo.
v2.0.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: braposo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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: braposo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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: braposo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.