Our take
Inactiveno commits in over a year- Activity
- 19
- Community
- 48
- Issues
- 21
- Pull requests
- 20
-2 stars in the last 30 days
PluginBase offers a focused approach to Python plugin loading, but its inactive maintenance status makes it a cautious choice for new dependencies.
Good fit if
- You need a small Python library for loading plugins from filesystem paths.
- Your application can assess and manage the risks of relying on a project with no recent commits or releases.
- You are comfortable reviewing the repository's license status, which is reported as NOASSERTION.
Look elsewhere if
- You need an actively maintained plugin framework or recent upstream issue and pull-request handling.
- Your adoption process requires a clearly asserted license.
- Your plugin system needs capabilities beyond the loading flow described in the project documentation.
All health signals
| Last commit | 2021-05-16 (5.4 years ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest 1.0.0, 2019-02-02) |
| Contributors | 7 (top contributor: 54% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 12 years |
Checked on 2026-10-16 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,138Forks
140Change since Nov 18, 2026: 0 stars·0 forks
Overview
PluginBase is a Python library for building flexible plugin systems. It gives an application a plugin namespace and a source that searches configured directories, so applications can load plugins without hard-coding each plugin into their own package.
It is aimed at Python developers adding extensions to an application. Plugins can be loaded through imports inside the plugin source context or directly with load_plugin.
Key Features
- Create a plugin base associated with an application package.
- Configure one or more filesystem search paths for plugins.
- Load a plugin by importing it within a plugin-source context.
- Load a plugin directly by name with
load_plugin. - Call the loaded plugin's functions from the application.
Use Cases
- An application developer can let users add Python extensions in configured directories.
- A team can split optional application capabilities into plugins loaded only when needed.
- A Python tool can support locally maintained plugins without importing each one into its main package.
What you need
Detected in the repository
- Python (from setup.py)
- A test suite
Getting Started
from pluginbase import PluginBase
plugin_base = PluginBase(package="yourapplication.plugins")
plugin_source = plugin_base.make_plugin_source(searchpath=["./path/to/plugins"])
with plugin_source:
from yourapplication.plugins import my_plugin
my_plugin.do_something_cool()
See the repository README for the alternative load_plugin approach and additional setup details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
The repository is marked inactive, with no commits in over a year and no releases in the past year. Seven contributors are recorded, and contributor concentration is not flagged, but there has been no recent issue or pull-request activity. Tests are present, while CI is not detected. The project identifies Python as its runtime; the supplied documentation does not specify other runtime or infrastructure requirements. The license is reported as NOASSERTION, so verify the applicable terms before adopting it.
Found this useful?
Share it with someone who would like pluginbase.