pmtiles
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/index.cjs | AI (source-diff): tsup/esbuild bundle output, not obfuscation; stable for this build tool. | ai | |
| source-diff | obfuscated-file:dist/esm/index.js | AI (source-diff): tsup/esbuild bundle output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/pmtiles.js | AI (source-diff): esbuild IIFE bundle, readable PMTiles logic. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 1 / 8 | |
| 4.4.0 | 1 / 8 | |
| 4.3.2 | 1 / 8 | |
| 4.3.1 | 1 / 8 | |
| 4.3.0 | 1 / 9 | |
| 4.2.1 | 1 / 9 | |
| 4.2.0 | 1 / 9 | |
| 4.1.0 | 1 / 9 | |
| 4.0.1 | 1 / 9 | |
| 4.0.0 | 1 / 9 |
v4.3.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.