@shogo-ai/sdk
Shogo Platform SDK - Zero-boilerplate auth and database for Shogo apps
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/organicParticlesShaders-DIva0vBO.d.cts | AI (source-diff): TypeScript declaration file with readable JSDoc comments; long-line trigger is a false positive for bundled .d.ts output. | ai | |
| source-diff | obfuscated-file:dist/organicParticlesShaders-DIva0vBO.d.ts | AI (source-diff): Same file as .d.cts counterpart; readable declaration content, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/organicParticlesShaders-goxTzdB6.d.cts | AI (source-diff): TypeScript declaration file with readable JSDoc comments; long-line trigger is a false positive for .d.ts files in this package. | ai | |
| source-diff | obfuscated-file:dist/organicParticlesShaders-goxTzdB6.d.ts | AI (source-diff): Same file (.d.ts variant); readable declaration file, not obfuscated code. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 1 / 22 | |
| 1.3.1 | 1 / 22 | |
| 1.3.0 | 1 / 22 | |
| 1.2.2 | 1 / 22 | |
| 1.2.1 | 1 / 22 | |
| 1.2.0 | 1 / 22 | |
| 1.1.2 | 1 / 20 | |
| 1.1.1 | 1 / 20 | |
| 1.1.0 | 1 / 16 | |
| 1.0.3 | 1 / 16 | |
| 1.0.2 | 1 / 16 | |
| 1.0.1 | 0 / 12 | |
| 1.0.0 | 0 / 12 | |
| 0.4.0 | 0 / 9 | |
| 0.3.1 | 0 / 9 | |
| 0.3.0 | 0 / 9 | |
| 0.1.0 | 0 / 3 |
v1.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.