@fjall/components-infrastructure
Published fjall infrastructure components and utilities.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:aws-lambda | AI (phantom-deps): aws-lambda is a runtime dep used in Lambda handlers; phantom-dep heuristic fires because it's loaded by convention. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is loaded via CDK/ts-node convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-cost-explorer | AI (phantom-deps): Framework-scoped AWS SDK package loaded by convention; stable false positive for this CDK package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped CDK library; missing public metadata is expected for org-internal packages. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.11.1 | 5 / 11 | |
| 2.9.1 | 5 / 11 | |
| 2.9.0 | 5 / 11 | |
| 2.8.0 | 5 / 11 | |
| 2.7.1 | 5 / 11 | |
| 2.7.0 | 5 / 11 | |
| 2.6.0 | 5 / 11 | |
| 2.5.0 | 5 / 11 | |
| 2.4.8 | 5 / 11 | |
| 2.4.7 | 5 / 11 | |
| 2.4.5 | 5 / 11 | |
| 2.4.4 | 5 / 11 | |
| 2.4.3 | 5 / 11 | |
| 2.4.2 | 5 / 11 | |
| 2.4.1 | 5 / 11 | |
| 2.4.0 | 5 / 11 | |
| 2.3.0 | 5 / 11 | |
| 2.2.0 | 5 / 11 | |
| 2.1.1 | 5 / 11 | |
| 1.1.0 | 5 / 11 | |
| 0.102.0 | 5 / 10 | |
| 0.100.0 | 5 / 10 | |
| 0.99.4 | 5 / 10 | |
| 0.99.3 | 5 / 10 | |
| 0.99.1 | 5 / 10 | |
| 0.96.0 | 6 / 9 | |
| 0.95.0 | 5 / 9 | |
| 0.94.1 | 5 / 9 | |
| 0.94.0 | 5 / 9 | |
| 0.89.6 | 5 / 9 | |
| 0.89.5 | 5 / 10 | |
| 0.89.2 | 5 / 10 | |
| 0.88.4 | 5 / 10 | |
| 0.88.3 | 5 / 10 | |
| 0.88.1 | 5 / 10 | |
| 0.51.0 | 8 / 11 | |
| 0.43.2 | 9 / 11 | |
| 0.43.0 | 9 / 11 | |
| 0.42.1 | 9 / 11 | |
| 0.41.1 | 9 / 11 | |
| 0.30.0 | 8 / 11 | |
| 0.29.4 | 8 / 11 | |
| 0.29.3 | 8 / 11 | |
| 0.29.2 | 8 / 11 | |
| 0.29.1 | 8 / 11 | |
| 0.26.11 | 9 / 11 |
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.88.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.88.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.