@serenityjs/plugins
Plugins allow developers to create server sided modifications or extensions to the base server software. SerenityJS provides a powerfull set of tools to allow full control over your server. We provide a TypeScript and JavaSample plugin template, which can
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@serenityjs/logger | AI (dependencies): Same-org sibling dependency in the SerenityJS monorepo; expected and stable across versions. | ai | |
| dependencies | unvetted-dep:@serenityjs/binarystream | AI (dependencies): Same-org sibling dependency in the SerenityJS monorepo; expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@serenityjs/protocol | AI (phantom-deps): Same-org sibling dep; declared but may be transitively used — stable false positive for this monorepo package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.8.20 | 5 / 6 | |
| 0.8.19 | 5 / 6 | |
| 0.8.18 | 5 / 6 | |
| 0.8.17 | 5 / 6 | |
| 0.8.16 | 5 / 6 | |
| 0.8.15 | 5 / 6 | |
| 0.8.14 | 5 / 6 | |
| 0.8.13 | 5 / 6 | |
| 0.8.12 | 5 / 6 | |
| 0.8.11 | 5 / 6 | |
| 0.8.10 | 5 / 6 | |
| 0.8.9 | 5 / 6 | |
| 0.8.8 | 5 / 6 | |
| 0.8.7 | 5 / 6 | |
| 0.8.6 | 5 / 6 | |
| 0.8.5 | 5 / 6 | |
| 0.8.4 | 5 / 6 | |
| 0.8.3 | 5 / 6 | |
| 0.8.2 | 5 / 6 | |
| 0.8.1 | 5 / 6 | |
| 0.8.0 | 5 / 6 | |
| 0.7.8 | 4 / 6 | |
| 0.7.7 | 4 / 6 | |
| 0.7.6 | 4 / 6 | |
| 0.7.5 | 4 / 6 | |
| 0.7.4 | 4 / 6 | |
| 0.7.3 | 4 / 6 | |
| 0.7.2 | 4 / 6 | |
| 0.7.1 | 4 / 6 | |
| 0.7.0 | 4 / 6 | |
| 0.6.4 | 4 / 6 | |
| 0.6.3 | 4 / 6 | |
| 0.6.2 | 4 / 6 | |
| 0.6.1 | 4 / 6 | |
| 0.6.0 | 4 / 6 | |
| 0.5.2 | 3 / 9 | |
| 0.5.1 | 3 / 9 | |
| 0.5.0 | 3 / 9 | |
| 0.4.4 | 2 / 8 | |
| 0.4.3 | 2 / 8 | |
| 0.4.2 | 2 / 8 | |
| 0.4.1 | 2 / 8 | |
| 0.4.0 | 2 / 8 | |
| 0.3.6 | 2 / 8 | |
| 0.3.5 | 2 / 8 | |
| 0.3.4 | 2 / 8 | |
| 0.3.3 | 2 / 8 | |
| 0.3.2 | 2 / 8 | |
| 0.3.1 | 2 / 8 | |
| 0.3.0 | 2 / 8 | |
| 0.2.4 | 2 / 8 |
v0.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.