← Home

@podlite/publisher

npm Repository Homepage

Publishing toolkit for Podlite — transform documents to HTML, generate sites

34
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zaggaz

Keywords

podlitepublisherpublishinghtmlmarkup-to-htmlstatic-sitedocumentationconvertergeneratormarkdowntransform

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): @podlite/publisher is a legitimate scoped package in an established monorepo; link-heavy README and missing repo URL are cosmetic issues, not spam indicators. ai

Versions (showing 34 of 34)

Version Deps Published
0.0.35 7 / 5
0.0.34 7 / 5
0.0.33 7 / 5
0.0.32 7 / 5
0.0.31 7 / 5
0.0.30 7 / 5
0.0.29 7 / 5
0.0.28 5 / 5
0.0.27 5 / 5
0.0.26 5 / 5
0.0.25 5 / 5
0.0.24 5 / 5
0.0.23 5 / 5
0.0.22 5 / 5
0.0.21 5 / 5
0.0.20 5 / 5
0.0.19 5 / 5
0.0.18 5 / 5
0.0.17 5 / 5
0.0.16 5 / 5
0.0.15 5 / 5
0.0.14 5 / 5
0.0.13 5 / 5
0.0.12 5 / 5
0.0.11 5 / 5
0.0.10 5 / 5
0.0.9 5 / 5
0.0.8 5 / 5
0.0.7 5 / 5
0.0.6 5 / 5
0.0.5 5 / 5
0.0.4 5 / 5
0.0.3 5 / 5
0.0.2 5 / 5

v0.0.35

1 finding
LOW No provenance attestation provenance

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

v0.0.34

1 finding
LOW No provenance attestation provenance

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

v0.0.33

1 finding
LOW No provenance attestation provenance

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

v0.0.32

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.