flatiron
An elegant blend of convention and configuration for building apps in Node.js and the browser
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): Legitimate maintainer transition within the flatiron/nodejitsu org in 2014; swaagie is a trusted long-standing publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Historical team change within the flatiron org; not indicative of takeover. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard CLI framework pattern for loading command modules from a configured source directory. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; last published 2014. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 4 / 5 | |
| 0.4.2 | 4 / 5 | |
| 0.4.1 | 4 / 5 | |
| 0.4.0 | 4 / 5 | |
| 0.3.11 | 4 / 5 | |
| 0.3.10 | 4 / 5 | |
| 0.3.9 | 4 / 5 | |
| 0.3.8 | 5 / 5 | |
| 0.3.7 | 5 / 5 | |
| 0.3.6 | 5 / 5 | |
| 0.3.5 | 5 / 5 | |
| 0.3.4 | 5 / 5 | |
| 0.3.3 | 5 / 5 | |
| 0.3.2 | 5 / 5 | |
| 0.3.0 | 5 / 5 | |
| 0.2.8 | 5 / 5 | |
| 0.2.7 | 5 / 5 | |
| 0.2.6 | 5 / 5 | |
| 0.2.5 | 5 / 5 | |
| 0.2.4 | 5 / 5 | |
| 0.2.3 | 5 / 5 | |
| 0.2.2 | 5 / 4 | |
| 0.2.1 | 5 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.17 | 5 / 1 | |
| 0.1.16 | 5 / 1 | |
| 0.1.15 | 5 / 1 | |
| 0.1.14 | 5 / 1 | |
| 0.1.13 | 5 / 1 | |
| 0.1.12 | 6 / 1 | |
| 0.1.11 | 6 / 1 | |
| 0.1.10 | 6 / 1 | |
| 0.1.9 | 6 / 1 | |
| 0.1.8 | 6 / 1 | |
| 0.1.7 | 6 / 1 | |
| 0.1.6 | 5 / 0 | |
| 0.1.5 | 5 / 0 | |
| 0.1.4 | 5 / 0 | |
| 0.1.3 | 5 / 0 | |
| 0.1.2 | 5 / 0 |
v0.4.3
2 findingsThis version was published by a different npm account than previous versions on 2014-12-16. 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.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-12-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-12-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-12-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-07-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-07-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-07-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-02-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2012-10-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2012-05-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2012-05-06. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2012-03-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2012-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.