@glimmer/program
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/prod/index.js | AI (source-diff): Rollup-minified prod build output, not obfuscation; stable for this package. | ai | |
| phantom-deps | phantom-dep:@glimmer/encoder | AI (phantom-deps): Internal monorepo dep, same org scope, stable across versions. | ai | |
| phantom-deps | phantom-dep:@glimmer/env | AI (phantom-deps): Internal monorepo dep, same org scope, stable across versions. | ai | |
| dependencies | unvetted-dep:@glimmer/encoder | AI (dependencies): Same-org sibling package in Glimmer VM monorepo. | ai | |
| dependencies | unvetted-dep:@glimmer/manager | AI (dependencies): Same-org sibling package in Glimmer VM monorepo. | ai | |
| dependencies | unvetted-dep:@glimmer/opcode-compiler | AI (dependencies): Same-org sibling package in Glimmer VM monorepo. | ai | |
| phantom-deps | phantom-dep:@glimmer/vm | AI (phantom-deps): Type-only/re-export usage common in this monorepo's packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Small internal build artifact package; not spam. | ai | |
| dependencies | unvetted-dep:@glimmer/vm | AI (dependencies): Same-org sibling package in Glimmer VM monorepo. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.94.10 | 6 / 9 | |
| 0.94.9 | 6 / 9 | |
| 0.94.8 | 6 / 9 | |
| 0.94.7 | 6 / 9 | |
| 0.94.6 | 6 / 9 | |
| 0.94.5 | 6 / 9 | |
| 0.94.4 | 6 / 9 | |
| 0.94.3 | 6 / 9 | |
| 0.94.2 | 6 / 9 | |
| 0.94.1 | 6 / 9 | |
| 0.94.0 | 6 / 9 | |
| 0.93.1 | 8 / 8 | |
| 0.93.0 | 8 / 8 | |
| 0.92.4 | 8 / 6 | |
| 0.92.3 | 8 / 6 | |
| 0.92.2 | 8 / 6 |
v0.94.10
2 findingsNewly 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.
v0.94.9
2 findingsNewly 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.
v0.94.8
2 findingsNewly 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.
v0.94.7
2 findingsNewly 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.
v0.94.6
2 findingsNewly 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.
v0.94.5
2 findingsNewly 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.
v0.94.4
2 findingsNewly 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.
v0.94.3
2 findingsNewly 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.
v0.94.2
2 findingsNewly 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.
v0.94.1
2 findingsNewly 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.
v0.94.0
2 findingsNewly 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.
v0.93.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.0
2 findingsNewly 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.
v0.92.4
2 findingsNewly 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.
v0.92.3
2 findingsNewly 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.
v0.92.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.