@symbo.ls/frank
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped org package (@symbo.ls) with established publisher; inflated semver reflects org-wide versioning scheme. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in a bundler/parser context to evaluate extracted variable values; consistent with the package's transformation purpose. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads resolved absolute paths for module inspection in a filesystem transformation tool; not arbitrary user input. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.14.0 | 4 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.6.6 | 3 / 0 | |
| 3.6.4 | 3 / 0 | |
| 3.6.1 | 3 / 0 |
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.