@teamplay/backend
Create new ShareDB backend instance
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:@startupjs/sharedb-mingo-memory | AI (dependencies): Same-org scoped fork of prior dependency, part of maintainer's own package family. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes TLS cert/key/ca from base64 config options — standard pattern, not a malicious payload. | ai | |
| phantom-deps | phantom-dep:@types/ioredis-mock | AI (phantom-deps): Type declaration package; not directly imported by convention. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 17 / 0 | |
| 0.4.0 | 16 / 0 | |
| 0.3.35 | 16 / 0 | |
| 0.3.30 | 16 / 0 | |
| 0.3.29 | 16 / 0 | |
| 0.3.28 | 16 / 0 | |
| 0.3.25 | 16 / 0 | |
| 0.3.20 | 16 / 0 | |
| 0.3.18 | 16 / 0 | |
| 0.3.17 | 16 / 0 | |
| 0.3.12 | 16 / 0 | |
| 0.3.7 | 16 / 0 | |
| 0.3.6 | 16 / 0 | |
| 0.3.5 | 16 / 0 | |
| 0.3.4 | 16 / 0 | |
| 0.3.3 | 16 / 0 | |
| 0.3.1 | 16 / 0 | |
| 0.3.0 | 16 / 0 | |
| 0.2.6 | 16 / 0 | |
| 0.2.5 | 16 / 0 | |
| 0.2.4 | 16 / 0 | |
| 0.2.3 | 16 / 0 | |
| 0.2.2 | 16 / 0 | |
| 0.2.1 | 16 / 0 | |
| 0.2.0 | 16 / 0 | |
| 0.1.16 | 16 / 0 | |
| 0.1.15 | 16 / 0 | |
| 0.1.14 | 16 / 0 | |
| 0.1.13 | 16 / 0 | |
| 0.1.12 | 16 / 0 | |
| 0.1.11 | 16 / 0 | |
| 0.1.10 | 16 / 0 | |
| 0.1.9 | 16 / 0 | |
| 0.1.8 | 16 / 0 | |
| 0.1.7 | 17 / 0 | |
| 0.1.6 | 17 / 0 | |
| 0.1.5 | 17 / 0 |
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.