← Home

@player-ui/stage-revert-data-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): Established monorepo publisher with 26 approved packages; likely CI environment change, not a supply-chain concern. ai
provenance no-provenance AI (provenance): Consistent across all @player-ui releases; org-level pattern, not a per-version risk. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo plugin; missing metadata is typical for this package family across 489 versions. ai
npm-metadata no-description AI (npm-metadata): Consistent pattern across @player-ui monorepo packages; not a spam indicator here. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages. ai
phantom-deps phantom-dep:tapable-ts AI (phantom-deps): Referenced in config files; typical for build-time hook wiring in monorepo plugins. ai

Versions (showing 23 of 23)

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

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

v0.15.5

1 finding
INFO No provenance attestation provenance

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

v0.10.4

1 finding
INFO No provenance attestation provenance

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

v0.10.3

1 finding
INFO No provenance attestation provenance

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

v0.10.2

1 finding
INFO No provenance attestation provenance

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

v0.10.1

1 finding
INFO No provenance attestation provenance

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

v0.10.0

1 finding
INFO No provenance attestation provenance

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

v0.9.1

1 finding
INFO No provenance attestation provenance

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

v0.8.0

1 finding
INFO No provenance attestation provenance

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

v0.7.3

1 finding
INFO No provenance attestation provenance

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