@tryghost/kg-parser-plugins
Plugins for parsing HTML back into Ghost Mobiledoc Cards
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 1 / 14 | |
| 4.3.1 | 1 / 14 | |
| 4.3.0 | 1 / 14 | |
| 4.2.25 | 1 / 14 | |
| 4.2.24 | 1 / 14 | |
| 4.2.10 | 1 / 10 | |
| 4.2.8 | 1 / 10 | |
| 4.2.7 | 1 / 10 | |
| 4.2.6 | 1 / 10 | |
| 4.2.5 | 1 / 10 | |
| 4.2.4 | 1 / 10 | |
| 4.2.3 | 1 / 10 | |
| 4.2.2 | 1 / 10 |
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.