@renseiai/plugin-linear
Linear issue tracker integration for AgentFactory — status transitions, agent sessions, work routing
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA attestation present; missing gitHead is a benign CI config change, not a supply chain concern for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation present; stable signal for this publisher's packages. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 2 / 3 | |
| 0.8.66 | 2 / 3 | |
| 0.8.65 | 2 / 3 | |
| 0.8.63 | 2 / 3 | |
| 0.8.62 | 2 / 3 | |
| 0.8.61 | 2 / 3 | |
| 0.8.60 | 2 / 3 | |
| 0.8.59 | 2 / 3 | |
| 0.8.58 | 2 / 3 | |
| 0.8.57 | 2 / 3 | |
| 0.8.56 | 2 / 3 | |
| 0.8.55 | 2 / 3 | |
| 0.8.54 | 2 / 3 | |
| 0.8.53 | 2 / 3 | |
| 0.8.52 | 2 / 3 | |
| 0.8.51 | 2 / 3 | |
| 0.8.50 | 2 / 3 | |
| 0.8.49 | 2 / 3 | |
| 0.8.48 | 2 / 3 | |
| 0.8.46 | 2 / 3 | |
| 0.8.45 | 2 / 3 | |
| 0.8.44 | 2 / 3 | |
| 0.8.43 | 2 / 3 | |
| 0.8.42 | 2 / 3 | |
| 0.8.41 | 2 / 3 | |
| 0.8.40 | 2 / 3 | |
| 0.8.39 | 2 / 3 | |
| 0.8.38 | 2 / 3 | |
| 0.8.37 | 2 / 3 | |
| 0.8.36 | 2 / 3 | |
| 0.8.35 | 2 / 3 | |
| 0.8.34 | 2 / 3 | |
| 0.8.33 | 2 / 3 | |
| 0.8.32 | 2 / 3 | |
| 0.8.31 | 2 / 3 | |
| 0.8.30 | 2 / 3 | |
| 0.8.29 | 2 / 3 | |
| 0.8.28 | 2 / 3 | |
| 0.8.27 | 2 / 3 | |
| 0.8.26 | 2 / 3 | |
| 0.8.25 | 2 / 3 | |
| 0.8.24 | 2 / 3 | |
| 0.8.23 | 2 / 3 | |
| 0.8.22 | 2 / 3 | |
| 0.8.21 | 2 / 3 | |
| 0.8.20 | 2 / 3 | |
| 0.8.19 | 2 / 3 | |
| 0.8.18 | 2 / 3 | |
| 0.8.17 | 1 / 3 | |
| 0.8.16 | 1 / 3 | |
| 0.8.15 | 1 / 3 | |
| 0.8.14 | 1 / 3 | |
| 0.8.13 | 1 / 3 | |
| 0.8.12 | 1 / 3 | |
| 0.8.11 | 1 / 3 | |
| 0.8.10 | 1 / 3 | |
| 0.8.9 | 1 / 3 | |
| 0.8.8 | 1 / 3 | |
| 0.8.7 | 1 / 3 | |
| 0.8.6 | 1 / 3 |
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.18
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.