israeli-banks-actual-budget-importer 1.0.0-beta.1

package/.yarnrc.yml

@@ -0,0 +1,3 @@
+yarnPath: .yarn/releases/yarn-4.7.0.cjs
+
+nodeLinker: node-modules

package/CHANGELOG.md

@@ -0,0 +1,6 @@
+# 1.0.0-beta.1 (2025-03-24)
+
+
+### Bug Fixes
+
+* **initial-commit:** restructure project files and update dependencies ([ad1abcf](https://github.com/tomerh2001/israeli-banks-actual-budget-importer/commit/ad1abcf4e405f2356342b684fff3773a92b3b4ce))

package/Dockerfile

@@ -0,0 +1,8 @@
+FROM alpine:latest
+
+ARG GH_REPO
+ARG RELEASE_NOTES
+
+LABEL org.opencontainers.image.source $GH_REPO
+
+CMD ["echo", "Hello World!"]

package/README.md

@@ -0,0 +1,25 @@
+# Israeli Banks → Actual Budget
+[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
+[![XO code style](https://shields.io/badge/code_style-5ed9c7?logo=xo&labelColor=gray)](https://github.com/xojs/xo)
+[![Snyk Security](../../actions/workflows/snyk-security.yml/badge.svg)](../../actions/workflows/snyk-security.yml)
+[![CodeQL](../../actions/workflows/codeql.yml/badge.svg)](../../actions/workflows/codeql.yml)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/tomerh2001/semantic-release-repo-template/badge)](https://securityscorecards.dev/viewer/?uri=github.com/tomerh2001/semantic-release-repo-template)
+
+This repository provides a simple script to import transactions from Israeli banks (via [israeli-bank-scrapers](https://github.com/eshaham/israeli-bank-scrapers)) into [Actual Budget](https://github.com/actualbudget/actual).
+
+## Features
+1. Supports all of the institutions that the [israeli-bank-scrapers](https://github.com/eshaham/israeli-bank-scrapers) library covers (Bank Hapoalim, Cal, Leumi, Discount, etc.).
+1. Automatically **creates new Actual accounts** if none exist.
+2. **Prevents duplicate transactions** using Actual’s [`imported_id`](https://actualbudget.org/docs/api/reference/#transactions) logic.
+3. Configurable via a single JSON file specifying bank credentials, start dates, etc.
+
+## Logging & Errors
+The script logs each step (connections, scraping, account creation, transaction import results). If any errors occur, they are printed to stderr.
+
+## Common error scenarios
+- Wrong credentials (scraper fails).
+- Actual Budget server is not running or wrong credentials (password).
+- Conflicting or missing environment/config.
+
+## Contributing
+Feel free to open pull requests and issues! Suggestions or improvements are welcome.

package/SECURITY.md

@@ -0,0 +1,48 @@
+# Security Policy
+
+## 1. Purpose
+
+This document provides guidelines and procedures for maintaining the security and integrity of the repository.
+
+## 2. Scope
+
+This policy applies to all contributors, maintainers, and users of the repository.
+
+## 3. Repository Security
+
+### 3.1. Access Control
+
+- Access to the repository is restricted to authorized personnel only. All contributors must have a valid and active GitHub account.
+- External collaborators should be granted access on a need-to-know basis and should be reviewed periodically.
+
+### 3.2. Encryption
+
+- All sensitive data stored in this repo must be encrypted using `git-crypt`.
+- Authorized users will be provided with decryption keys. These keys must not be shared, stored publicly, or embedded in code.
+
+### 3.3. Code Review
+
+- All pull requests (PRs) must undergo a code review by at least one other member before being merged.
+- PRs with changes to cryptographic routines or handling of encrypted data must be reviewed by a security expert.
+
+## 4. Reporting Security Issues
+
+- If you discover a vulnerability or security issue, please create an issue on the GitHub repository. Label it as `security` for easy identification.
+- Do not disclose details of the vulnerability in public forums, chats, or other public channels.
+
+## 5. Patch Management
+
+- All contributors are encouraged to regularly fetch updates from the main branch and ensure their local copy is updated to benefit from security patches.
+
+## 6. Compliance
+
+- Contributors found to be in violation of this policy may have their access revoked.
+- Users and maintainers are encouraged to report any non-compliance to this policy.
+
+## 7. Review and Updates
+
+This policy will be reviewed annually or after any significant incident.
+
+## 8. Contact
+
+For any queries or concerns regarding this security policy, eat a biscuit. (tomerh2001@gmail.com)