@splendidlabz/third-party
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package from known author; missing metadata is expected for private org packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Private org package; missing description is consistent across versions. | ai | |
| phantom-deps | phantom-dep:http-errors | AI (phantom-deps): Referenced in config/middleware files; stable false positive for this internal utility package. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is a logging formatter typically used via config, not direct import; stable false positive here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.5.3 | 7 / 3 | |
| 1.5.2 | 8 / 2 | |
| 1.5.1 | 8 / 2 | |
| 1.5.0 | 8 / 2 | |
| 1.4.0 | 8 / 2 | |
| 1.3.18 | 8 / 2 | |
| 1.3.17 | 8 / 2 | |
| 1.3.16 | 8 / 2 | |
| 1.3.15 | 8 / 2 | |
| 1.3.14 | 8 / 2 | |
| 1.3.13 | 8 / 2 | |
| 1.3.12 | 8 / 2 | |
| 1.3.11 | 8 / 2 | |
| 1.3.10 | 8 / 2 | |
| 1.3.9 | 8 / 2 | |
| 1.3.8 | 8 / 2 | |
| 1.3.7 | 8 / 2 | |
| 1.3.6 | 8 / 2 | |
| 1.3.5 | 8 / 2 | |
| 1.3.4 | 8 / 2 | |
| 1.3.3 | 8 / 2 | |
| 1.3.2 | 8 / 2 | |
| 1.3.1 | 8 / 2 | |
| 1.3.0 | 8 / 2 | |
| 1.2.0 | 8 / 2 | |
| 1.1.1 | 6 / 2 | |
| 1.1.0 | 6 / 2 | |
| 1.0.0 | 4 / 2 |
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.