@aguspe/tiler-server
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:react | AI (phantom-deps): Server package bundles/SSR usage; react declared as dep but not directly imported in server code. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Same as react — SSR/bundled usage pattern for this server package. | ai | |
| phantom-deps | phantom-dep:bcryptjs | AI (phantom-deps): Auth utility likely used indirectly via compiled dist; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/cookie | AI (phantom-deps): Fastify plugin registered at runtime; not directly imported in analyzed source. | ai | |
| phantom-deps | phantom-dep:@aguspe/tiler-viewer | AI (phantom-deps): Same-org sibling dep; used indirectly via bundled output. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 15 / 6 | |
| 1.1.0 | 15 / 6 | |
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.