Skip to content

Latest commit

 

History

History
228 lines (228 loc) · 9.15 KB

File metadata and controls

228 lines (228 loc) · 9.15 KB

v0.3.0 - 2025-10-27

  • Normalize distribution/package naming to pyexploitdb and refactor public APIs to snake_case.
  • Harden data handling with strict validation, concurrency for missing CVE hydration, and improved error reporting.
  • Add smoke-test suite, documentation updates, and guidance for pre-release verification.

v0.2.10 - 2024-05-08

  • Last commit by sscottgvit: Fix typo'

v0.2.11 - 2024-05-08

  • Last commit by GitHub Action: Bump version to 0.2.10 and update ChangeLog

v0.2.12 - 2024-05-08

  • Last commit by GitHub Action: Bump version to 0.2.11 and update ChangeLog

v0.2.13 - 2024-05-08

  • Last commit by GitHub Action: Bump version to 0.2.12 and update ChangeLog

v0.2.14 - 2024-05-08

  • Last commit by sscottgvit: Merge branch 'master' of github.com:GoVanguard/pyExploitDb

v0.2.15 - 2024-05-08

  • Last commit by : Updated exploit database mappings

v0.2.16 - 2024-05-10

  • Last commit by : Updated exploit database mappings

v0.2.17 - 2024-05-12

  • Last commit by : Updated exploit database mappings

v0.2.18 - 2024-05-19

  • Last commit by : Updated exploit database mappings

v0.2.19 - 2024-05-26

  • Last commit by : Updated exploit database mappings

v0.2.20 - 2024-06-02

  • Last commit by : Updated exploit database mappings

v0.2.21 - 2024-06-09

  • Last commit by : Updated exploit database mappings

v0.2.22 - 2024-06-16

  • Last commit by : Updated exploit database mappings

v0.2.23 - 2024-06-23

  • Last commit by : Updated exploit database mappings

v0.2.24 - 2024-06-30

  • Last commit by : Updated exploit database mappings

v0.2.25 - 2024-07-07

  • Last commit by : Updated exploit database mappings

v0.2.26 - 2024-07-14

  • Last commit by : Updated exploit database mappings

v0.2.27 - 2024-07-21

  • Last commit by : Updated exploit database mappings

v0.2.28 - 2024-07-28

  • Last commit by : Updated exploit database mappings

v0.2.29 - 2024-08-04

  • Last commit by : Updated exploit database mappings

v0.2.30 - 2024-08-11

  • Last commit by : Updated exploit database mappings

v0.2.31 - 2024-08-18

  • Last commit by : Updated exploit database mappings

v0.2.32 - 2024-08-25

  • Last commit by : Updated exploit database mappings

v0.2.33 - 2024-09-01

  • Last commit by : Updated exploit database mappings

v0.2.34 - 2024-09-08

  • Last commit by : Updated exploit database mappings

v0.2.35 - 2024-09-15

  • Last commit by : Updated exploit database mappings

v0.2.36 - 2024-09-22

  • Last commit by : Updated exploit database mappings

v0.2.37 - 2024-09-29

  • Last commit by : Updated exploit database mappings

v0.2.38 - 2024-10-06

  • Last commit by : Updated exploit database mappings

v0.2.39 - 2024-10-13

  • Last commit by : Updated exploit database mappings

v0.2.40 - 2024-10-20

  • Last commit by : Updated exploit database mappings

v0.2.41 - 2024-10-27

  • Last commit by : Updated exploit database mappings

v0.2.51 - 2024-10-28

  • Last commit by : Updated exploit database mappings

v0.2.52 - 2024-10-28

  • Last commit by sscott: Updates to code

v0.2.53 - 2024-10-28

  • Last commit by : Updated exploit database mappings

v0.2.54 - 2024-11-10

  • Last commit by : Updated exploit database mappings

v0.2.55 - 2024-11-17

  • Last commit by : Updated exploit database mappings

v0.2.56 - 2024-11-24

  • Last commit by : Updated exploit database mappings

v0.2.57 - 2024-12-01

  • Last commit by : Updated exploit database mappings

v0.2.58 - 2024-12-08

  • Last commit by : Updated exploit database mappings

v0.2.59 - 2024-12-15

  • Last commit by : Updated exploit database mappings

v0.2.60 - 2024-12-22

  • Last commit by : Updated exploit database mappings

v0.2.61 - 2024-12-29

  • Last commit by : Updated exploit database mappings

v0.2.62 - 2025-01-05

  • Last commit by : Updated exploit database mappings

v0.2.63 - 2025-01-12

  • Last commit by : Updated exploit database mappings

v0.2.64 - 2025-01-19

  • Last commit by : Updated exploit database mappings

v0.2.65 - 2025-01-26

  • Last commit by : Updated exploit database mappings

v0.2.66 - 2025-02-02

  • Last commit by : Updated exploit database mappings

v0.2.67 - 2025-02-09

  • Last commit by : Updated exploit database mappings

v0.2.68 - 2025-02-16

  • Last commit by : Updated exploit database mappings

v0.2.69 - 2025-02-23

  • Last commit by : Updated exploit database mappings

v0.2.70 - 2025-03-02

  • Last commit by : Updated exploit database mappings

v0.2.71 - 2025-03-09

  • Last commit by : Updated exploit database mappings

v0.2.72 - 2025-03-16

  • Last commit by : Updated exploit database mappings

v0.2.73 - 2025-03-23

  • Last commit by : Updated exploit database mappings

v0.2.74 - 2025-03-30

  • Last commit by : Updated exploit database mappings

v0.2.75 - 2025-04-06

  • Last commit by : Updated exploit database mappings

v0.2.76 - 2025-04-13

  • Last commit by : Updated exploit database mappings

v0.2.77 - 2025-04-20

  • Last commit by : Updated exploit database mappings

v0.2.78 - 2025-04-27

  • Last commit by : Updated exploit database mappings

v0.2.79 - 2025-05-04

  • Last commit by : Updated exploit database mappings

v0.2.80 - 2025-05-11

  • Last commit by : Updated exploit database mappings

v0.2.81 - 2025-05-18

  • Last commit by : Updated exploit database mappings

v0.2.82 - 2025-05-25

  • Last commit by : Updated exploit database mappings

v0.2.83 - 2025-06-01

  • Last commit by : Updated exploit database mappings

v0.2.84 - 2025-06-08

  • Last commit by : Updated exploit database mappings

v0.2.85 - 2025-06-15

  • Last commit by : Updated exploit database mappings

v0.2.86 - 2025-06-22

  • Last commit by : Updated exploit database mappings

v0.2.87 - 2025-06-29

  • Last commit by : Updated exploit database mappings

v0.2.88 - 2025-07-06

  • Last commit by : Updated exploit database mappings

v0.2.89 - 2025-07-13

  • Last commit by : Updated exploit database mappings

v0.2.90 - 2025-07-20

  • Last commit by : Updated exploit database mappings

v0.2.91 - 2025-07-27

  • Last commit by : Updated exploit database mappings

v0.2.92 - 2025-08-03

  • Last commit by : Updated exploit database mappings

v0.2.93 - 2025-08-10

  • Last commit by : Updated exploit database mappings

v0.2.94 - 2025-08-17

  • Last commit by : Updated exploit database mappings

v0.2.95 - 2025-08-24

  • Last commit by : Updated exploit database mappings

v0.2.96 - 2025-08-31

  • Last commit by : Updated exploit database mappings

v0.2.97 - 2025-09-07

  • Last commit by : Updated exploit database mappings

v0.2.98 - 2025-09-14

  • Last commit by : Updated exploit database mappings

v0.2.99 - 2025-09-21

  • Last commit by : Updated exploit database mappings

v0.2.100 - 2025-09-28

  • Last commit by : Updated exploit database mappings

v0.2.101 - 2025-10-05

  • Last commit by : Updated exploit database mappings

v0.2.102 - 2025-10-12

  • Last commit by : Updated exploit database mappings

v0.2.103 - 2025-10-19

  • Last commit by : Updated exploit database mappings

v0.2.104 - 2025-10-26

  • Last commit by : Updated exploit database mappings

v0.3.1 - 2025-11-19

  • Last commit by sscott-tantalumlabs: Updated exploit database mappings

v0.3.2 - 2025-11-23

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.3 - 2025-11-30

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.4 - 2025-12-07

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.5 - 2025-12-14

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.6 - 2025-12-21

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.7 - 2025-12-28

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.8 - 2026-01-04

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.9 - 2026-01-11

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.10 - 2026-01-18

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.11 - 2026-01-25

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.12 - 2026-02-01

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.13 - 2026-02-08

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.14 - 2026-02-15

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.15 - 2026-02-22

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.16 - 2026-03-01

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.17 - 2026-03-08

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.18 - 2026-03-15

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.19 - 2026-03-22

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.20 - 2026-03-29

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.21 - 2026-04-05

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.22 - 2026-04-12

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.23 - 2026-04-19

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.24 - 2026-04-26

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.25 - 2026-05-03

  • Last commit by GitHub Action: Updated exploit database mappings

v0.3.26 - 2026-05-10

  • Last commit by GitHub Action: Updated exploit database mappings