← Home

@player-ui/markdown-plugin

npm
23
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

adierkensplayer-oss

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): player-oss has 56 approved packages; missing gitHead reflects a CI change, not a supply-chain risk for this monorepo. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; missing metadata is typical for @player-ui scoped packages, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent pattern across @player-ui monorepo packages; not a malice signal. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a well-known build-time implicit dep; stable false positive for this package. ai
phantom-deps phantom-dep:tapable-ts AI (phantom-deps): Referenced in config/build files; stable false positive for this package. ai

Versions (showing 23 of 23)

Version Deps Published
1.0.1 3 / 2
1.0.0 3 / 2
0.15.5 3 / 2
0.15.4 3 / 2
0.15.3 3 / 2
0.15.2 3 / 2
0.15.1 3 / 2
0.15.0 3 / 2
0.14.1 3 / 2
0.14.0 3 / 2
0.13.0 3 / 2
0.12.0 3 / 2
0.11.2 3 / 2
0.11.1 3 / 2
0.11.0 3 / 2
0.10.4 3 / 2
0.10.3 3 / 2
0.10.2 3 / 2
0.10.1 3 / 2
0.10.0 3 / 2
0.9.1 3 / 2
0.8.0 3 / 2
0.7.3 3 / 0

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.15.5

1 finding
LOW No provenance attestation provenance

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

v0.10.4

1 finding
LOW No provenance attestation provenance

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

v0.10.3

1 finding
LOW No provenance attestation provenance

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

v0.10.2

1 finding
LOW No provenance attestation provenance

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

v0.10.1

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.3

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.