@serenityjs/protocol
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-velocity monorepo with 883 versions; rapid publishes are normal for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; not a risk indicator for this established package. | ai | |
| dependencies | unvetted-dep:@serenityjs/nbt | AI (dependencies): Internal sibling dep within the SerenityJS monorepo; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo workspace package; sparse metadata is expected, not indicative of spam. | ai | |
| dependencies | unvetted-dep:@serenityjs/binarystream | AI (dependencies): Internal sibling dep within the SerenityJS monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@serenityjs/raknet | AI (dependencies): Internal sibling dep within the SerenityJS monorepo; stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this monorepo package; not a malice indicator. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.8.21 | 3 / 6 | |
| 0.8.20 | 3 / 6 | |
| 0.8.19 | 3 / 6 | |
| 0.8.18 | 3 / 6 | |
| 0.8.17 | 3 / 6 | |
| 0.8.16 | 3 / 6 | |
| 0.8.15 | 3 / 6 | |
| 0.8.14 | 3 / 6 | |
| 0.8.13 | 3 / 6 | |
| 0.8.12 | 3 / 6 | |
| 0.8.11 | 3 / 6 | |
| 0.8.10 | 3 / 6 | |
| 0.8.9 | 3 / 6 | |
| 0.8.8 | 3 / 6 | |
| 0.8.7 | 3 / 6 | |
| 0.8.6 | 3 / 6 | |
| 0.8.5 | 3 / 6 | |
| 0.8.4 | 3 / 6 | |
| 0.8.3 | 3 / 6 |
v0.8.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.