← Home

issue-parser

Parser for Github, GitLab and Bitbucket issues actions, references and mentions

17
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pvdlgsemantic-release-botgr2mtravi

Keywords

bitbucketcloseduplicatefixgithubgitlabissuesmentionsparserprpull-requestreferencesresolve

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer from original author pvdlg to semantic-release org; semantic-release-bot is a highly trusted publisher (975 approved). ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (travi, semantic-release-bot, gr2m) are all known semantic-release org members; legitimate org transfer. ai

Versions (showing 17 of 17)

Version Deps Published
7.0.2 5 / 7
7.0.1 5 / 8
7.0.0 5 / 8
6.0.0 5 / 5
5.0.0 5 / 5
4.0.0 5 / 5
3.0.1 5 / 5
3.0.0 5 / 5
2.3.0 4 / 5
2.2.0 4 / 5
2.1.0 4 / 5
2.0.1 1 / 5
2.0.0 1 / 5
1.0.3 1 / 5
1.0.2 1 / 5
1.0.1 1 / 8
1.0.0 1 / 8

v7.0.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: semantic-release-bot → GitHub Actions (on 2026-05-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.

v7.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.0

2 findings
HIGH Publisher changed: pvdlg → semantic-release-bot (on 2024-03-14) provenance

This version was published by a different npm account than previous versions on 2024-03-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.