Package Health Score

81 / 100

security
No known security issues
popularity
Small
maintenance
Healthy
community
Active

Explore Similar Packages

Popularity

Small

GitHub Stars: 115
Forks: 48
Contributors: 20

Direct Usage Popularity

Based on project statistics from the GitHub repository for the PyPI package premise, we found that it has been starred 115 times.

Security

No known security issues

Security and license risk for latest version

Release Date: Oct 29, 2024
Direct Vulnerabilities: 0
C
0
H
0
M
0
L
Indirect Vulnerabilities: 0
C
0
H
0
M
0
L
License Risk: 0
H
0
M
0
L

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

BSD-3-Clause

Security Policy

We found a way for you to contribute to the project! Looks like premise is missing a security policy.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

Keep your project free of vulnerabilities with Snyk

Maintenance

Healthy

Commit Frequency

Open Issues: 21
Open PR: 0
Last Release: 10 days ago
Last Commit: 20 days ago

Further analysis of the maintenance status of premise based on released PyPI versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that premise demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Active

Readme: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 20
Funding: No

With more than 10 contributors for the premise repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Python Versions Compatibility: <3.12,>=3.10

Age: 1 year
Latest Release: 10 days ago
Dependencies: 15 Direct
Versions: 49
Maintainers: 1
Wheels: OS Independent

Readme

`premise`

PRospective EnvironMental Impact AsSEssment

Coupling the ecoinvent database with projections from Integrated Assessment Models (IAM)

premise is a Python tool for prospective life cycle assessment. It allows users to project the ecoinvent 3 database into the future, using scenarios from Integrated Assessment Models (IAMs). It does so by modifying the ecoinvent database to reflect projected energy policy trajectories, include emerging technologies, modify market shares as well as technologies' efficiency.

Among others, it can be used to assess the environmental impacts of future energy systems, and to compare different energy policies. It includes a set of IAM scenarios and a set of tools to create custom scenarios.

The tool was designed to be user-friendly and to allow for reproducible results. While it is built on the brightway2 framework, its outputs can naturally be used in Activity Browser, but also in other LCA software, such as SimaPro, OpenLCA, or directly in Python.

The tool is described in the following scientific publication: Sacchi et al, 2022. If this tool helps you in your research, please consider citing this publication.

Also, use the following references to cite the scenarios used with the tool:

REMIND scenarios: Baumstark et al. REMIND2.1: transformation and innovation dynamics of the energy-economic system within climate and sustainability limits, Geoscientific Model Development, 2021.
IMAGE scenarios: Stehfest, Elke, et al. Integrated assessment of global environmental change with IMAGE 3.0: Model description and policy applications. Netherlands Environmental Assessment Agency (PBL), 2014.
TIAM-UCL scenarios:

Models

The tool currently supports the following IAMs:

Model	Description
REMIND	REMIND (Regionalized Model of Investment and Development) is an integrated assessment model that combines macroeconomic growth, energy system, and climate policy analysis. It is designed to analyze long-term energy transition pathways, accounting for technological, economic, and environmental factors. REMIND simulates how regions invest in different technologies and energy resources to balance economic growth and climate targets, while considering factors like energy efficiency, emissions, and resource availability. The model is particularly strong in its detailed representation of energy markets and macroeconomic interactions across regions, making it valuable for global climate policy assessments.
IMAGE	IMAGE (Integrated Model to Assess the Global Environment) is a comprehensive IAM developed to explore the interactions between human development, energy consumption, and environmental systems over the long term. It focuses on assessing how land use, food systems, energy systems, and climate change interact under different policy scenarios. The model integrates biophysical processes, such as land-use change and greenhouse gas emissions, with socio-economic drivers like population growth and economic development. IMAGE is commonly used for analyzing sustainable development strategies, climate impacts, biodiversity loss, and exploring mitigation and adaptation options.
TIAM-UCL	TIAM-UCL (TIMES Integrated Assessment Model by University College London) is a global energy system model based on the TIMES (The Integrated MARKAL-EFOM System) framework, developed to evaluate long-term decarbonization pathways for global energy systems. It provides detailed insights into energy technology options, resource availability, and emission reduction strategies under various climate policy scenarios. The model focuses on the trade-offs and synergies between energy security, economic costs, and environmental outcomes. TIAM-UCL is frequently used to analyze scenarios consistent with the Paris Agreement and examine technological innovation's role in mitigating climate change globally.

What's new in 2.1.4?

Integration of TIAM-UCL scenarios

What's new in 2.1.1?

Ecoinvent 3.10 support
Adds inventories on ammonia production
Fixes issues with scaling applied to PV systems

What's new in 2.1.0?

More efficient use of memory.
Easier syntax for using custom scenarios.

What's new in 2.0.0?

Adds .write_db_to_olca(), which produces a slightly modified version of a Simapro CSV database file which can then be imported in OpenLCA. The use of the SimaPro_Import.csv mapping file must be selected.
Marginal mixes were wrong because the average lifetime of the mix was calculated using the technology-specific lead time values instead of lifetime values.
Fix issue with CCS implementation in IMAGE scenarios
Fix several issues with external/custom scenarios linking algorithm.
Drops DAC efficiency improvement based on cumulated deployment. Uses directly efficiency variables now (if provided).
Improves documentation for consequential modelling.
Code-breaking change: update functions are now called like so: .update(xxx). For example, to update the electricity sector: .update(["electricity",]). To update all sectors: .update().
Changes minimum Python requirement to 3.10

What's new in 1.8.0?

Added support for brightway 2.5 (requires bw2data >= 4.0.0)
Added support for Python 3.11
Uses bw2io 0.8.10
Adds electricity storage in electricity markets -- see docs
Adds scenario explorer dashboard

What's new in 1.5.0?

Added support for ecoinvent 3.9 and 3.9.1
Added support for ecoinvent 3.8 and 3.9/3.9.1 consequential -- see docs
Added REMIND SSP1 and SSP5 scenarios -- see docs
Updated GAINS emission factors, using GAINS-EU and GAINS-IAM -- see docs
Added new inventories for DAC and DACCS -- see docs
Added new inventories for EPR and SMR nuclear reactors -- see EPR inventories and SMR inventories
Made mapping to new IAM models easier -- see docs
Better logging of changes made to the ecoinvent database -- see docs

What's new in 1.3.0?

Added support for user-generated scenarios (see docs and notebook)
Updated REMIND scenarios to REMIND v.3.0

Documentation

https://premise.readthedocs.io/en/latest/

Objective

The objective is to produce life cycle inventories under future energy policies, by modifying the inventory database ecoinvent 3 to reflect projected energy policy trajectories.

Requirements

Python 3.10 or 3.11
License for ecoinvent 3. Please note that the ecoinvent database is not included in this package. Also, read ecoinvent's GDPR & EULA.
Some IAM output files come with the library and are located by default in the subdirectory "/data/iam_output_files". If you wish to use those files, you need to request (by email) an encryption key from the developers. A file path can be specified to fetch IAM output files elsewhere on your computer.
brightway2 (optional). If you want to use the results in the Brightway 2 framework 8and Activity Browser), you need bw2data <4.0.0. To produce Brightway 2.5-compatible databases, you need bw2data >=4.0.0.

How to install this package?

Two options:

From Pypi:

pip install premise

will install the package and the required dependencies.

A development version with the latest advancements (but with the risks of unseen bugs), is available from Anaconda Cloud:

conda install -c conda-forge premise

How to use it?

The best way is to follow the examples from the Jupyter Notebook.

Support

Do not hesitate to contact romain.sacchi@psi.ch.

Contributors

Maintainers

Contributing

See contributing.

References

License

premise dependencies

bottleneck bw2data cryptography datapackage pandas platformdirs premise-gwp prettytable pyarrow pycountry pyyaml requests schema tqdm unfold

FAQs

What is premise?

Coupling IAM output to ecoinvent LCA database ecoinvent for prospective LCA. Visit Snyk Advisor to see a full health score report for premise, including popularity, security, maintenance & community analysis.

Is premise popular?

The python package premise receives a total of 1,313 weekly downloads. As such, premise popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is premise well maintained?

We found that premise demonstrated a healthy version release cadence and project activity. It has a community of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is premise safe to use?

The python package premise was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 1 November-2024, at 03:57 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Direct Usage Popularity

Security and license risk for latest version

Commit Frequency

Embed Package Health Score Badge

Keep your project healthy

Check your requirements.txt

Snyk Vulnerability Scanner

Readme

premise

PRospective EnvironMental Impact AsSEssment

Coupling the ecoinvent database with projections from Integrated Assessment Models (IAM)

Models

What's new in 2.1.4?

What's new in 2.1.1?

What's new in 2.1.0?

What's new in 2.0.0?

What's new in 1.8.0?

What's new in 1.5.0?

What's new in 1.3.0?

Documentation

Objective

Requirements

How to install this package?

How to use it?

Support

Contributors

Maintainers

Contributing

References

License

premise dependencies

FAQs

What is premise?

Is premise popular?

Is premise well maintained?

Is premise safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues

`premise`