@pbvision/fastify-firestore-service
Web Framework using Fastify and Firestore ORM
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:word-wrap | AI (phantom-deps): Declared dependency; used indirectly via ua-parser-js and other transitive deps. | ai | |
| phantom-deps | phantom-dep:ua-parser-js | AI (phantom-deps): Declared dependency; used indirectly through fastify plugins and utilities. | ai | |
| phantom-deps | phantom-dep:@fastify/static | AI (phantom-deps): Declared dependency; used indirectly through fastify plugin ecosystem. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.0.50 | 12 / 26 | |
| 0.0.49 | 12 / 26 | |
| 0.0.48 | 12 / 26 | |
| 0.0.47 | 12 / 26 | |
| 0.0.46 | 12 / 26 | |
| 0.0.45 | 12 / 26 | |
| 0.0.44 | 12 / 26 | |
| 0.0.43 | 12 / 26 | |
| 0.0.42 | 12 / 26 | |
| 0.0.41 | 12 / 26 | |
| 0.0.40 | 12 / 26 | |
| 0.0.39 | 12 / 26 | |
| 0.0.38 | 12 / 26 | |
| 0.0.37 | 11 / 26 | |
| 0.0.36 | 11 / 26 | |
| 0.0.35 | 11 / 25 | |
| 0.0.34 | 11 / 25 | |
| 0.0.33 | 11 / 25 | |
| 0.0.32 | 11 / 25 | |
| 0.0.31 | 11 / 25 | |
| 0.0.30 | 11 / 25 | |
| 0.0.29 | 11 / 25 | |
| 0.0.28 | 11 / 25 | |
| 0.0.27 | 11 / 25 | |
| 0.0.26 | 11 / 25 | |
| 0.0.25 | 11 / 25 | |
| 0.0.24 | 11 / 25 | |
| 0.0.23 | 11 / 25 | |
| 0.0.22 | 12 / 25 | |
| 0.0.21 | 12 / 25 | |
| 0.0.20 | 12 / 25 | |
| 0.0.19 | 12 / 25 | |
| 0.0.18 | 12 / 25 | |
| 0.0.17 | 12 / 25 | |
| 0.0.16 | 12 / 25 | |
| 0.0.15 | 12 / 25 | |
| 0.0.14 | 12 / 25 | |
| 0.0.13 | 12 / 25 | |
| 0.0.12 | 12 / 25 | |
| 0.0.11 | 12 / 25 | |
| 0.0.10 | 12 / 25 | |
| 0.0.9 | 13 / 23 | |
| 0.0.8 | 13 / 23 | |
| 0.0.7 | 13 / 23 | |
| 0.0.6 | 13 / 23 | |
| 0.0.5 | 13 / 23 | |
| 0.0.4 | 13 / 23 | |
| 0.0.3 | 13 / 23 |
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.