figma-js
A simple wrapper for the Figma API
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from jongold to chrisdrackett occurred in 2019; chrisdrackett has 37 approved packages and a clean track record. Legitimate historical maintainer transition. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Preinstall script only checks for Yarn as the package manager and throws a descriptive error — no network access or arbitrary code execution. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency used by this TypeScript package; the phantom-dep finding is a false positive due to TypeScript build indirection. | ai | |
| provenance | missing-githead | AI (provenance): Established package with 33 versions and clean history; missing gitHead reflects a publish environment change, not a supply chain compromise signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): figma-js has never used Sigstore provenance attestation; this is a consistent pattern across its 33 versions and not a security risk for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.16.0 | 1 / 17 | |
| 1.15.0 | 1 / 17 | |
| 1.14.0 | 1 / 17 | |
| 1.13.0 | 1 / 17 | |
| 1.12.0 | 1 / 17 | |
| 1.11.0 | 1 / 17 | |
| 1.10.1 | 1 / 17 | |
| 1.10.0 | 1 / 17 | |
| 1.9.0 | 1 / 17 | |
| 1.8.5 | 1 / 17 | |
| 1.8.4 | 1 / 17 | |
| 1.8.3 | 1 / 17 | |
| 1.8.2 | 1 / 17 | |
| 1.8.1 | 1 / 17 | |
| 1.8.0 | 1 / 17 | |
| 1.7.0 | 1 / 17 | |
| 1.6.1 | 1 / 17 | |
| 1.6.0 | 1 / 17 | |
| 1.5.1 | 1 / 17 | |
| 1.5.0 | 1 / 17 | |
| 1.4.0 | 1 / 17 | |
| 1.3.4 | 1 / 17 | |
| 1.3.3 | 1 / 17 | |
| 1.3.2 | 1 / 17 | |
| 1.3.1 | 1 / 17 | |
| 1.3.0 | 1 / 17 | |
| 1.2.3 | 1 / 17 | |
| 1.2.2 | 1 / 17 | |
| 1.2.1 | 1 / 17 | |
| 1.2.0 | 1 / 17 | |
| 1.0.1 | 1 / 17 | |
| 1.0.0 | 1 / 17 |
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
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: chrisdrackett.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
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: chrisdrackett.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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: chrisdrackett.
v1.8.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: chrisdrackett.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
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: chrisdrackett.
v1.8.0
3 findingsThis version was published by a different npm account than previous versions on 2019-08-15. This could indicate a legitimate maintainer transition or an account compromise.
[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: chrisdrackett.
v1.7.0
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: jongold.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
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: jongold.
v1.5.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: jongold.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
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: jongold.
v1.3.4
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: jongold.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsScript: node -e "if(process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('figma-js must be installed with Yarn: https://yarnpkg.com/')"
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsScript: node -e "if(process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('figma-js must be installed with Yarn: https://yarnpkg.com/')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsScript: node -e "if(process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('figma-js must be installed with Yarn: https://yarnpkg.com/')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: node -e "if(process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('figma-js must be installed with Yarn: https://yarnpkg.com/')"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.