@flxbl-io/sfprofiles
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Worker thread loader pattern resolving workerData.path; stable and expected for this package's architecture. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is listed as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 17 / 22 | |
| 5.2.1 | 17 / 22 | |
| 5.2.0 | 17 / 22 | |
| 5.1.4 | 17 / 22 | |
| 5.1.3 | 17 / 22 | |
| 5.1.2 | 17 / 22 | |
| 5.0.0 | 17 / 22 |
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.